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
Bulk actions in Oban Web work based on the selected items. We recently struggled with a situation where the worker uniqueness settings were not correct and there were a lot of jobs arriving in the queue with the same parameters. We had to delete jobs cyclically via a manual, hand-crafted SQL query.
In addition to being able to operate on selected items, the interface should also allow actions on all filtered jobs - such as cancelling all jobs - without having to select them.
The text was updated successfully, but these errors were encountered:
@sorentwo cool, thanks!
BTW, is it safe to delete rows in oban_jobs manually? I noticed that Oban.cancel_all_jobs/1 not only updates the status but it also triggers Notifier to perform some additional work.
BTW, is it safe to delete rows in oban_jobs manually?
It depends on what the jobs are and if the side-effect of deleting them would matter. The primary purpose of events for cancel_job and cancel_all_jobs is for distributed process killing, batch callbacks, etc.
Bulk actions in Oban Web work based on the selected items. We recently struggled with a situation where the worker uniqueness settings were not correct and there were a lot of jobs arriving in the queue with the same parameters. We had to delete jobs cyclically via a manual, hand-crafted SQL query.
In addition to being able to operate on selected items, the interface should also allow actions on all filtered jobs - such as cancelling all jobs - without having to select them.
The text was updated successfully, but these errors were encountered: