Recover an Uncertain Submission

Investigate an interrupted XL1 submission without creating accidental duplicates.

Owner: XYO Layer One maintainers · Last verified: September 17, 2026

An application can lose its response after a remote operation succeeds. Treat that result as unknown, not failed.

1

Stop automatic retries

Do not rebuild, re-sign, or resubmit immediately. A new transaction may create a second valid operation.

2

Preserve public evidence

Retain the transaction hash, payload hashes, signer address, network identity, and the time of the attempt. Never include secrets in diagnostic records.

3

Query through the SDK

Use gateway.connection.viewer?.transaction.byHash(hash) from @xyo-network/xl1-sdk. Check finalized state and any related payload evidence.

4

Decide from observed state

If finalized, report success. If pending, continue observation. If absent, apply the application's documented expiry and resubmission policy before creating a new operation.