Five retention jobs have no attempt timeout

Open
#3,304 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
csharp
Domain
backend

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

area:jobs type:bug

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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from fluentcms/FluentCMS

All issues in fluentcms/FluentCMS

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.