Oh looks like i didnt consider "soft deleted" jobs in the fetching, very sorry for that.
So what happns when you delete a job in webint is that that jobid is noted in a separate mongo collection deleted_jobs and the same job is deleted from the jobs collection. (You can use mongo compass to connect to the webint db to investigate if you like).
This all while the actual ffastrans job in cache/jobs stays on the filesystem, so the jobfetcher sees the deleted jos in their folders.
Until i fixed it you have following options
Get rid of the deleted jobs in ffastrans cache/jobs folder
Undelete all jobs by either connecting to the database and purge the deleted collection or just delete webint database as whole
emcodem wrote: ↑Thu Apr 16, 2026 11:13 am
@DCCentR
Oh looks like i didnt consider "soft deleted" jobs in the fetching, very sorry for that.
So what happns when you delete a job in webint is that that jobid is noted in a separate mongo collection deleted_jobs and the same job is deleted from the jobs collection. (You can use mongo compass to connect to the webint db to investigate if you like).
This all while the actual ffastrans job in cache/jobs stays on the filesystem, so the jobfetcher sees the deleted jos in their folders.
Until i fixed it you have following options
Get rid of the deleted jobs in ffastrans cache/jobs folder
Undelete all jobs by either connecting to the database and purge the deleted collection or just delete webint database as whole
Thanks, I took the easiest route and deleted the webint database