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
With the current removal criteria of jobs, if a queue is removed from the configuration the Jobs that were in it will not be deleted because that queue is no longer processed.
How can we remove them?
Maybe the best approach is to create a command to remove them.
After all, the queues are defined in the configuration and can be removed only from the configuration.
So, a developer action is required.
It seems logic to let the developer run the command to remove the Jobs that are still in the removed queues.
(Question: when a Jb is created, does the bundle checks if the queue really exist?)
The text was updated successfully, but these errors were encountered:
With the current removal criteria of jobs, if a queue is removed from the configuration the Jobs that were in it will not be deleted because that queue is no longer processed.
How can we remove them?
Maybe the best approach is to create a command to remove them.
After all, the queues are defined in the configuration and can be removed only from the configuration.
So, a developer action is required.
It seems logic to let the developer run the command to remove the Jobs that are still in the removed queues.
(Question: when a Jb is created, does the bundle checks if the queue really exist?)
The text was updated successfully, but these errors were encountered: