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
Is your feature request related to a problem? Please describe.
Sometimes you want to cancel a Job which is running in the JobQueue. This may be because it is not needed and takes up too many resources, or because it got into a bad state and just needs purging.
Describe the solution you'd like
A new mutation, e.g. cancelJob or deleteJob. Not sure if 2 separate mutations are needed yet - needs more research.
The text was updated successfully, but these errors were encountered:
Done a bit more digging here. Here's a real scenario that I have right now (and have had reported too by users on Slack):
A particular job in the queue gets stuck in the RUNNING state. This probably occurs due to it being running when the server is shut down, and for some reason the teardown logic is not being completed (which is supposed to set all RUNNING jobs back to PENDING).
Henceforth the job is listed as running (e.g. in the Admin UI) with no way to cancel or remove short of physically deleting the job from storage (e.g. deleting the row in the DB table).
I think we only need a cancelJob mutation, since "deletion" is already handled by the existing removeSettledJobs mutation (cancelled jobs would also be considered settled).
Is your feature request related to a problem? Please describe.
Sometimes you want to cancel a Job which is running in the JobQueue. This may be because it is not needed and takes up too many resources, or because it got into a bad state and just needs purging.
Describe the solution you'd like
A new mutation, e.g.
cancelJob
ordeleteJob
. Not sure if 2 separate mutations are needed yet - needs more research.The text was updated successfully, but these errors were encountered: