> For the complete documentation index, see [llms.txt](https://docs.xyo.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xyo.network/developers/cookbook/recover-an-uncertain-submission.md).

# 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.

{% stepper %}
{% step %}

## Stop automatic retries

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

{% step %}

## 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.
{% endstep %}

{% step %}

## Query through the SDK

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

{% step %}

## 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.
{% endstep %}
{% endstepper %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.xyo.network/developers/cookbook/recover-an-uncertain-submission.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.