Invoice Sync Succeeds Only After Background Retry
Med.DashboardsWaiting
Mission
- Incident
Background retries often create the difference between a healthy release and a flaky one, especially in billing-adjacent flows
- Goal
Trigger the sync action, observe the retry-backed lifecycle, and prove the final done state appears without sleep-heavy logic
- Pass condition
Trigger the real sync action
What counts
- Trigger the real sync action
- idle -> running -> done lifecycle
- budget-left metric is preserved at 1 after retries
Constraints1 rules + 1 mutation note
Rules
- Do not ignore retry budget metrics when claiming success
Mutation
- Budget card layout can change while metric semantics stay fixed
Hint 1
Action: Trigger the real sync action.
Hint 2
Assertion: Assert idle -> running -> done lifecycle.
Hint 3
Assertion: Assert budget-left metric is preserved at 1 after retries.