Retries and idempotency

Retries improve delivery only when the endpoint can safely receive the same logical job more than once. Make the receiver idempotent before broadening a retry policy.

Prerequisites

• Identify the schedule and each side effect it can create.
• Decide which failures are transient for this endpoint.
• Choose a stable deduplication key and retention window.

Workflow

1. Inspect recent history to classify failures.
2. Add endpoint idempotency and test duplicate requests.
3. Update only the schedule's retry policy.
4. Verify a controlled transient failure and its eventual success.
5. Recheck history for attempt count, delay, and final outcome.