Business situation
A request times out even though the provider may have processed it. A fresh request can repeat an uncertain action.
The key decision
Separate accepted, processing and confirmed outcomes. Query uncertain results rather than treating timeout as failure.
How implementation works
Keep stable request identifiers and a timeline of queries and receipts. Validate state transitions and review unresolved execution.
Business value and evolution
Teams distinguish pending confirmation from safe retries. Acceptance covers timeouts, duplicates and out-of-order notifications.