Skip to content

fix: include failed end-user CRA send jobs in retry flow - #374

Merged
mdiapenabc merged 1 commit into
devfrom
feature/retry-failed-job-include-poll-cra-system-error
Jun 22, 2026
Merged

fix: include failed end-user CRA send jobs in retry flow#374
mdiapenabc merged 1 commit into
devfrom
feature/retry-failed-job-include-poll-cra-system-error

Conversation

@mdiapenabc

Copy link
Copy Markdown
Collaborator

Description

  • Extends the retry-failed flow to recover failed user-initiated CRA send jobs in addition to existing failed CRON jobs.
  • This ensures system-error CRA send attempts can be retried automatically.

What Changed

  • Updated retry filters in backend/src/jobs/jobs.service.ts for getFailedJobs() and hasStuckOrFailedJobs().
  • Added an END_USER allowlist for retryable job types, currently including SEND_CRA_FILE.
  • Updated unit test expectations in backend/src/jobs/jobs.service.spec.ts to match the new retry criteria.

How To Test

  • Create a failed top-level SEND_CRA_FILE job with jobTrigger=END_USER.
  • Run the retry-failed job and confirm that run is reset to RUNNING and executed.
  • Verify failed top-level CRON jobs are still retried as before.

Expand retry-failed job selection to include top-level failed END_USER SEND_CRA_FILE runs while keeping CRON retries unchanged, so system-error CRA sends can be recovered automatically.
@mdiapenabc
mdiapenabc merged commit 7f3926f into dev Jun 22, 2026
20 checks passed
@mdiapenabc
mdiapenabc deleted the feature/retry-failed-job-include-poll-cra-system-error branch June 22, 2026 17:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants