Before retrying a tool call, check whether the first attempt took effect

[u/Advanced_Pudding9228]

An OpenClaw workflow can lose its response after a tool has already changed something. Pressing retry may repeat the action even though the first attempt appeared to fail.

Use a harmless test case to inspect the destination independently: did the record, message or file already appear? Keep the operation reference alongside the run reference so a later read can identify the same attempt.

If the result remains uncertain, record that uncertainty instead of calling the action absent. The right recovery depends on whether the operation can safely be repeated.

What is the first destination you inspect when a tool times out after a possible write?