Before retrying, check whether the action already happened
A connection can fail after the destination processes a payment or sends a message. Repeating the request blindly can duplicate its effects. Separate confirmed, confirmed not executed and unknown outcomes before deciding what to do next.
The destination is in Spanish. This is a waitlist, not guaranteed immediate access or a free plan.
Situations to review
A payment request times out and the automation cannot confirm the result.
Check the provider’s authorized records using the operation reference and exact amount, currency and recipient. Review retry rules for that endpoint and API version, including supported idempotency identifiers, parameter matching and retention. Do not create a new key to disguise a retry or reuse a key for a different intention.
A confirmed operation is not submitted again. If the destination lookup is inconclusive, keep the result unknown and stop for review rather than treating silence as failure.
An email request loses its response, leaving it unclear whether the message was sent.
Look for the message or operation identifier and the email system’s history. Recipient, subject and approximate time help an investigation but do not uniquely identify an operation by themselves. Also check pending actions. Absence from a partial search is not proof that nothing was sent.
Sufficient evidence of sending prevents a blind repeat. An inconclusive lookup stays unknown: a fresh approval does not prove the earlier attempt had no effect.
A record change loses its response after possibly triggering other work.
Compare the destination record and history with the proposed change. Setting a field, incrementing a balance and creating an object are different operations. Check version conflicts and secondary effects such as notifications or derived records.
HTTP or a connector name does not establish business-level idempotency. An applied change is not blindly repeated, and uncertainty about downstream effects remains explicit.
How to evaluate the work
- Describe the intention, destination system, resource, operation reference, parameters and external effect. Define what evidence would establish that execution began or completed. A generic error message does not locate the failure.
- Classify outcomes by evidence: confirmed not executed when that can be demonstrated, confirmed when the destination establishes the effect, and unknown when the response or history is insufficient. A timeout alone cannot choose between these states.
- Check that service’s rules for idempotency, identifier retention, parameters, concurrency and limits. Stripe API v1 and v2 have different documented behavior; do not generalize it to other providers. Think² can organize collaborators, groups and context with compatible models and authorized tools; each collaborator can have their own computer. These capabilities do not establish technical deduplication or exactly-once execution. External actions require approval and current evidence.
- Template: intention; destination; reference; parameters; evidence and timestamp; confirmed/not executed/unknown status; documented retry protection; decision; owner; applicable approval. Fictional example: a test record in PagoDemo contains order ORD-204 for 48 units of test currency. After a timeout, its test history shows that exact reference and parameters as approved: do not repeat. If the lookup is inconclusive, mark the outcome unknown and investigate, rather than submit a new charge. This is a fictional documented scenario, not a payment test or integration. Stop if parameters change, duplicate protection expires or the destination cannot be verified.
Frequently asked questions
Does a timeout mean nothing happened?
No. A response can be lost after an action completes. Check the destination system and retain an unknown outcome when evidence is insufficient.
Does an idempotency key protect a retry forever?
Do not assume that. Scope, retention, API version and parameter handling depend on the service. Reusing a key outside its documented conditions may not prevent a new operation.
Does Think² approval prevent duplicates?
Approval authorizes a specific external action; it does not establish that a previous attempt never happened or guarantee technical deduplication. First verify the evidence and the action being approved.
Sources and scope
- Stripe — Idempotent requests — Stripe-specific rules distinguish API v1 and v2; not proof of a Think² integration or implementation.
- AWS — Making retries safe with idempotent APIs — Design guidance for identifiers and uncertain retry outcomes, not a guarantee for a particular workflow.
- RFC9110 §9.2.2 — HTTP idempotency concerns intended method effects; not a classification of every business action.
Keep exploring
The destination is in Spanish. This is a waitlist, not guaranteed immediate access or a free plan.