-
-
Notifications
You must be signed in to change notification settings - Fork 363
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
flow children with groups are not visible in bullboard #770
Comments
Hello, I ran into the same issue earlier. In our case, we are not using FlowProducer but just groups along with priority. group: {
id: campaignId,
priority: priority
} I can confirm the issue remains even if the priority is removed. I didn't dig deeper, but I assume since the library is using the standard bullmq library, those jobs are not returned by the library. I think a PR would be great if you already have a fix; otherwise, I can take a look at it by the end of the week. On a side note, I checked the official UI at taskforce.sh, and Cheers, |
So, how i can support groups in bull-borad? |
How can I get the bullmq-pro? |
It's an important feature to understand how to view the division in Bull-Board according to the groups in Bull-Pro. Taskforce using a free token or are interested in using Taskforce on a trial basis. Need to log in and get a token for npm registry We can see the division according to the groups in Redis Insight. This is helpful for us, and we would like to know how to support this feature in Bull-Board as well? Thanks for the answer and for the great library! |
Yeah, it seems that "groups" were implemented by adding the group name into the name of the queue. If you have time, I'll more than happy to review a PR for this. |
I'll try to see how I can support it and will update you. |
When using flows and groups (which is a bullmq pro feature), flow children jobs are not visible.
For example adding a flow like this (without children.*.opts.group):
results in:
But adding a flow with children.*.opts.group like this:
results in this
Bullmq processes all jobs, flow children are simply not visible in bullboard.
Are pro features out of context in bullboard or is there interest to have that handled?
I'll be more than happy to open a PR to fix this if bullboard intend to support this feature :)
The text was updated successfully, but these errors were encountered: