Skip to content

fix: improve CRA send batch failure handling and UI feedback#387

Merged
mdiapenabc merged 4 commits into
devfrom
fix/send-cra-batch-job-failure-handling
Jun 25, 2026
Merged

fix: improve CRA send batch failure handling and UI feedback#387
mdiapenabc merged 4 commits into
devfrom
fix/send-cra-batch-job-failure-handling

Conversation

@mdiapenabc

Copy link
Copy Markdown
Collaborator

Description

Fixes CRA send job failure handling so batches show the correct status and comments, UI messages use batch number, and the running banner clears when the job fails or completes.

What Changed

  • Write failure system comments on the batch, not batch details
  • Set batch status to System Error when send fails (including from Pending)
  • Call onFailure when send setup (onStart) fails
  • Show batch number in send CRA messages and banner (not internal id)
  • Hide running banner when job fails, succeeds, or errors; reset stuck running state

How to Test

  1. Fail a CRA send and confirm batch shows System Error + system comment on Batch Requests (not on Batch Details)
  2. Confirm send messages/banner use batch number from the table
  3. While sending, banner should show; after failure or success, banner should disappear
  4. Refresh after a failed send: banner should not stay stuck
  5. Run send-cra-file.handler.spec.ts and related backend tests

Record job failures on batch system comments and system_error status,
invoke onFailure when send setup fails, show batch numbers in send
messages, and hide the running banner when the job fails or completes.
Reload batch requests and details when a send job fails so updated
system_error status and system comments appear without a manual refresh.
@mdiapenabc mdiapenabc merged commit fdb3da4 into dev Jun 25, 2026
19 checks passed
@mdiapenabc mdiapenabc deleted the fix/send-cra-batch-job-failure-handling branch June 25, 2026 02:34
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