An ERP agent timed out after the write. What should it do next?

说明与用途

当ERP代理在写入后超时时，系统无法确认操作是否成功，导致不确定性和潜在重复。测试表明，通过读回可恢复结果，防止重复。

问题

When an ERP agent times out after a write, the caller cannot determine if the write succeeded, leading to uncertainty and potential duplicate actions.

结果

The test demonstrated that unknown outcomes can be resolved through authoritative read-back, preventing duplicate writes and enabling safe recovery.

工作流

• Record target environment, business object, operation, approved input revision and stable request identity before dispatch.
• Recheck target and authorization at execution; if input changed, obtain decision on changed request.
• After dispatch, classify outcome as confirmed, definite rejection, or unknown.
• For unknown outcomes, perform lookup using stable business reference or correlation method.
• Provide operator with original request, last known state, and evidence for investigation.
• If compensating action needed, give it its own identity and authorization and retain original result for later review.

证据

A timeout is a poor instruction to retry a business transaction. The receiver might have committed the change before the response disappeared.

来源

The timeout case made one fixture write, then raised an exception before returning its receipt. The controller retained an unknown outcome.

来源

Read-only reconciliation recovered the receipt and verification moved the case to its accepted state.

来源

For an unresolved outcome, give the operator the original request, last known state and evidence needed to investigate.

来源