You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SRY :D I just noticed that the job name does not have to be the same as the queue name.
Hey!
Since I use different Workers for each process because it's not possible to filter jobs by custom fields, it would be very good if we could set a global concurrency flag.
I really don't want to set up multiple servers or oversize a single one for a worst-case concurrency scenario.
Perhaps an optional job name that can be filtered would also be a good option, if that would be more feasible. :D
The text was updated successfully, but these errors were encountered:
dotMortis
changed the title
Global concurrency
Global concurrency || Optional job names
Jun 23, 2021
dotMortis
changed the title
Global concurrency || Optional job names
Global concurrency || Optional filterable job names
Jun 23, 2021
SRY :D I just noticed that the job name does not have to be the same as the queue name.
Hey!
Since I use different Workers for each process because it's not possible to filter jobs by custom fields, it would be very good if we could set a global concurrency flag.
I really don't want to set up multiple servers or oversize a single one for a worst-case concurrency scenario.
Perhaps an optional job name that can be filtered would also be a good option, if that would be more feasible. :D
The text was updated successfully, but these errors were encountered: