Trouble Cancelling Jobs with Filters – Always Says 0 Matched
Hey everyone,
I'm trying to cancel a batch of jobs using the "Cancel all jobs matching filters" option, and I’ve set up filters like path, not running, scheduled before now, etc.
But every time I try, the confirmation popup says “0 jobs matched the filters,” even though I see jobs in the list that clearly match.
Here’s a sample of the filter object I’m using:
{
"workspace": "sample-workspace",
"scriptPathExact": "f/services/sample_service",
"running": false,
"isSkipped": false,
"hasNullParent": true,
"suspended": false,
"scheduledForBeforeNow": true
}
Maybe I’m not fully understanding how job selection works with the filters. Could someone share an example or explain what I might be missing?
Appreciate any help!1 Reply
Hello! Are you on windmill cloud? Otherwise could you share the windmill version you're running?
When you click on the "Cancel all jobs matching filters", the button on the modal should show you how many potential jobs you 're trying to cancel and the toast tells you how many were actually canceled by your request. It is possible that the jobs ended before you could cancel them.
Also, only running or queued jobs can be canceled, perhaps the jobs you see listed are already completed jobs?