Design retry and idempotency controls for AI-triggered actions.

Instruction: Explain stable operation IDs, payload binding, bounded retries, and reconciliation after an uncertain write.

Context: Design retries so repeated tool calls do not create duplicate actions or turn timeouts into false failure reports.

Updated

Official answer available

Read the opening below, then unlock the full answer and practical guidance.

I would assign an operation ID when the user intends an action, before execution. Retries retain that ID and the same payload. The service records the ID, request fingerprint, and outcome; reuse with a different payload is rejected.

For a single database write, I would record the operation...

Your preparation path

Work through these questions in order. Read the answer aloud, then explain it in your own words.

Related Questions