Five retention jobs have no attempt timeout
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
Research direction
Start with the job registrations in src/FluentCMS.Core/DependencyInjection/FluentCmsServiceCollectionExtensions.cs:309 and :262-282, then read the retention loop in ActivityLog/ActivityRetentionJob.cs:53-70 and the related runner issues #3266, #3276, and #3285. Add a 10-minute attempt timeout for each of the five named jobs and check that timed-out work resumes on a later run without dead-lettering. Add a test that lists built-in jobs lacking timeouts.
Written by the indexing model from the issue text.
Description
Problem
ActivityRetentionJob is registered without AttemptTimeout (src/FluentCMS.Core/DependencyInjection/FluentCmsServiceCollectionExtensions.cs:309), unlike JobRetentionJob and OutboxPruneJob, and the runner has no default. Its delete is batched and honours cancellation (ActivityLog/ActivityRetentionJob.cs:53-70) but the loop has no total bound. TrashPurgeJob, OidcPruneJob, UnverifiedMembersJob and IdempotencyRetentionJob are registered the same way (:262-282).
Proposal
Give the five jobs a 10-minute AttemptTimeout; each continues on its next run.
Done together with #3266, #3276 and #3285, which change the same runner and registrations.
Acceptance
- Each retention job has an attempt timeout
- A run stopped by the timeout leaves the remainder for the next run and is not dead-lettered
- A test that lists registered built-in jobs without a timeout
Found in the code review of 17 Nov 2026.
- 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