> For the complete documentation index, see [llms.txt](https://guide.scribe.gov.sg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.scribe.gov.sg/tips-and-tricks/retry-saving-your-session.md).

# Retry Saving your Session

#### What is this for?

Scribe uploads the audio from your conversation to our system in real-time. When your internet connection is poor or unstable, this upload process may be interrupted, which results in missing portions in your transcript.

This feature gives you the option to retry the upload process when saving your session, so you have the best chance of saving a complete recording.

{% hint style="info" %}
The retry option will only appear if there's audio data that failed to upload when saving your session.
{% endhint %}

#### How do I retry saving a session?

<figure><img src="https://2400606950-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFaQZ82l2KjVefurxtBBp%2Fuploads%2FzDAOzaLAOkPBsPFHrFwS%2Fimage.png?alt=media&amp;token=60f118d0-dfad-44d4-9f52-5358f6a57303" alt="" width="188"><figcaption></figcaption></figure>

1. Click `Save` as you normally would after your session
2. If your audio fails to upload within 30 seconds of clicking `Save`, you'll see two options:
   1. **Try again:** Attempt to upload your remaining audio again
      1. If this does not work, try moving to somewhere with better reception or switching to a different internet connection, then try again.
   2. **Save as is:** Save your session with just the audio that's already uploaded successfully

{% hint style="info" %}
Do not close your Scribe tab before retrying — Any audio that failed to upload the first time will be lost permanently if the tab is closed.
{% endhint %}


---

# 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://guide.scribe.gov.sg/tips-and-tricks/retry-saving-your-session.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.
