A job that ignores its cancellation token holds its worker forever
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 56/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- csharp
- Domain
- backend, devops, observability
Research direction
Read src/FluentCMS.Core/Jobs/JobExecutor.cs around lines 101 and 213, then inspect JobTimeoutTests.AJobThatIgnoresItsTokenStopsBeingRenewedAndIsTakenOverWhenItsLeaseLapses and compare the hand-off behavior in OutboxDrainer. Trace how attempt timeout and grace are handled; done means the acceptance cases pass and abandoned invocations are counted by a metric.
Written by the indexing model from the issue text.
Description
Problem
JobExecutor (src/FluentCMS.Core/Jobs/JobExecutor.cs:101,213) awaits the job's invocation directly. When the attempt timeout fires, the lease lapses and another worker takes the job, but the first worker stays in its await (see JobTimeoutTests.AJobThatIgnoresItsTokenStopsBeingRenewedAndIsTakenOverWhenItsLeaseLapses). Two such attempts stop the default queue (scheduled publish, retention, trash purge) on every instance until restart, and /health/ready reports Degraded only after 15 minutes. OutboxDrainer already hands off and waits with a limit.
Proposal
Run the invocation through a hand-off and WaitAsync(limit + grace); on time-out abandon it, settle the attempt as failed, free the worker, and count abandoned runs.
Acceptance
- A job that ignores its token frees its worker after its limit plus grace
- A metric counts abandoned invocations
Found in the code review of 17 Nov 2026 (B3).
- Dominant language
- C#
- Stars
- 569
- Forks
- 107
- Avg merge
- 2h 49m
- Merged PRs (30d)
- 397
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from fluentcms/FluentCMS
-
area:host area:operations type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area:build security type:chore
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area:sdk security type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area:content security type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
area:build type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
All issues in fluentcms/FluentCMS
Similar issues
-
bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
microsoft/microsoft-ui-reactor#1567 ·
Maintainers usually reply within 1 day
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P2
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
openclaw/openclaw-windows-node#2287 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
kind:ux needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
elsa-workflows/elsa-foundation#4742 ·
Maintainers usually reply within 1 day
-
priority:P2
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
enhancement good first issue help wanted new-language
Difficulty 2/5 1-3 hours Newbie friendliness 82/100