Retry Failed Individual Registrations Without Resubmitting the Entire Batch
When one or more mentor rows display an error state in the Batch Submission Progress Widget, a retry action (button or tap) is available per failed row. Activating retry re-invokes the Bulk Registration Service for only the affected mentor IDs, using the same activity template from the original submission. Successfully retried rows transition to success state. Rows that fail again remain in error state with an updated error message. The coordinator can also choose to retry all failed rows in one action.
User Story
Acceptance Criteria
- Given at least one mentor row is in error state after a bulk submission, when the coordinator taps the retry action on that row, then only that mentor's activity insert is resubmitted
- Given a retry submission succeeds, when the result is received, then the row transitions from error to success state and a delegation_grants record is created
- Given a retry submission fails again, when the error is returned, then the row remains in error state with an updated error reason
- Given multiple rows are in error state, when the coordinator taps 'Retry All Failed', then all error-state rows are resubmitted simultaneously
- Given successful rows exist when retries are triggered, when retries complete, then previously successful rows are unaffected and retain their success state
Business Value
Transient network failures are common in mobile environments. Without granular retry, a single failed row in a 30-mentor batch forces the coordinator to reconstruct the entire submission or manually identify and re-enter the missed record — both of which defeat the efficiency goal of bulk registration. Targeted retry keeps the coordinator productive and ensures eventual completeness without redundant data entry.