🏠 Overview › 👥 User Roles ›📖 Retry Failed Sync Records

Retry Failed Sync Records

When individual records fail to sync (due to authentication errors, network timeouts, API rate limits, or malformed payloads), they remain in a 'failed' state in the sync log and are flagged in the integration status dashboard. The accounting sync orchestrator implements exponential backoff for automatic retries, but administrators need the ability to manually retry after resolving the root cause. The integration status screen exposes a list of all failed records with their error details. Administrators can select one or more failed records and trigger an immediate retry via the accounting API gateway. Each retry attempt is logged as a new entry in the sync log with a reference to the original attempt.

HIGH story-accounting-system-integration-organization-administrator-005 5 pts
5
Story Points
High
Priority
Accounting System Integration
Feature

User Story

As a user
I want to identify records that failed to sync to the accounting system and retry them individually or in bulk after the underlying issue has been resolved
So that So that approved reimbursements and honorariums that were not posted due to temporary connectivity or API errors are eventually recorded in the accounting system without requiring manual data re-entry

Acceptance Criteria

  • Given the integration status dashboard shows failed records, when the administrator clicks 'View Failed Records', then a list of all failed sync attempts is shown with error messages and record details
  • Given the failed records list is displayed, when the administrator selects individual records and clicks 'Retry Selected', then the accounting sync orchestrator attempts to re-send those records to the accounting API gateway
  • Given the failed records list is displayed, when the administrator clicks 'Retry All Failed', then all records in the failed queue are retried in a single batch
  • Given a retry attempt succeeds, when the result is processed, then the record is removed from the failed queue and the sync log entry is updated to 'succeeded' with a reference to the retry event
  • Given a retry attempt fails again, when the result is processed, then the record remains in the failed queue with the new error message appended and the retry count incremented
  • Given the automatic exponential backoff is active for a record, when the administrator manually retries it, then the manual retry takes precedence and the backoff timer resets after the manual attempt

Business Value

Without a retry mechanism, failed sync records require manual data re-entry by finance teams — exactly the problem this integration is designed to eliminate. Retry capability ensures that transient failures (network outages, API downtime, rate limiting) do not result in permanent gaps in accounting records, protecting the integrity of financial data and the timeliness of volunteer reimbursement payments.

Components

Accounting System Integration
Related Feature
Organization Administrator
User Role