Skip to content

Resolve timeout ambiguity before repeating a table operation

Distinguish no response, received output and committed local state after an interruption.

Guides

Resolve timeout ambiguity before repeating a table operation — what should the operator record?

A timeout says that the caller did not observe a normal completion; it does not always reveal what happened on the other side. Before retrying, inspect the local ledger and any actual receipt available. Keep uncertain outcomes explicit so recovery does not duplicate an append or overwrite a valid artifact.

Practical operations check
Distinguish no response, received output and committed local state after an interruption.
Record operation_key, input_revision and intended_output without assuming the operation failed before any work occurred. For a local transformation, intended output can be a staged file path and expected manifest update; recording both clarifies which part of the operation is uncertain.
Record whether completion was established, safely reconciled or remains unknown, avoiding an unsupported reconstruction of events during the timeout. The supported conclusion may be safely reconciled despite unknown original completion; that is more accurate than claiming proof that the first operation never happened.
01 / Guides

Name the interrupted operation

Record operation_key, input_revision and intended_output without assuming the operation failed before any work occurred. For a local transformation, intended output can be a staged file path and expected manifest update; recording both clarifies which part of the operation is uncertain.

02 / Guides

Inspect local evidence

Check whether a response file, receipt or committed output revision exists; distinguish a partially written artifact from a complete accepted result. A file existing on disk does not establish that validation or commit completed; inspect its parser result and associated commit marker before treating it as accepted.

03 / Guides

Choose a safe branch

If completion remains unknown, preserve the uncertainty and use a new recovery operation reference rather than marking the original definitely failed. A recovery branch can reference uncertain_operation_key while keeping its own receipt and artifact identity, making the ambiguity visible without inventing a precise execution history.

04 / Guides

Compare retry results

Reconcile any authorized retry with existing accepted membership and keep duplicate or conflicting rows in separate exception classes. If the retry yields the same identifiers with changed fields, preserve that conflict for review rather than assuming it is a duplicate that can be discarded.

05 / Guides

Close the ambiguity

Record whether completion was established, safely reconciled or remains unknown, avoiding an unsupported reconstruction of events during the timeout. The supported conclusion may be safely reconciled despite unknown original completion; that is more accurate than claiming proof that the first operation never happened.

Keep the boundaries clear.

  • Distinguish no response, received output and committed local state after an interruption.
  • Operational record: Name the interrupted operation. Context badges do not certify access.

Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.

Primary references

Documentation reviewed 2026-11-15. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.

Know what social media shows about you.
Start with a question.

Get started
montage