> 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/help/my-transcript-is-still-processing.md).

# My Transcript is still processing

### Understanding Processing Times

In general, transcripts will take about **one-tenth of the session time** to process.

<table><thead><tr><th width="220.984375">For a session duration of...</th><th>Transcript processing will take...</th></tr></thead><tbody><tr><td>30 mins</td><td>~3 mins</td></tr><tr><td>60 mins</td><td>~6 mins</td></tr><tr><td>90 mins</td><td>~9 mins</td></tr></tbody></table>

***

### Understanding The Different Saving States

After recording a session, Scribe processes your audio into text. During this process, you may see your session card undergo different states. Here's what each one means —&#x20;

<table><thead><tr><th width="339.3359375">Screen</th><th>What it means</th></tr></thead><tbody><tr><td><img src="https://2400606950-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFaQZ82l2KjVefurxtBBp%2Fuploads%2FnZVcGfrndtRUq0W8jnNb%2Funknown.png?alt=media&amp;token=620da5be-cda5-42fe-82ca-ba0ef7d4f4cc" alt=""></td><td>Transcript is processing, it will take ~one-tenth of the session duration to complete processing. <br><br>This is normal behaviour — View the transcript on scribe.gov.sg on your laptop when processing is done.</td></tr><tr><td><img src="https://2400606950-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFaQZ82l2KjVefurxtBBp%2Fuploads%2FaDOGJnLcFXIUa28LR8Xt%2Funknown.png?alt=media&amp;token=75817980-5f26-4297-81bd-a30f19d29bbb" alt=""></td><td>Session was interrupted when saving. <br><br>Recover the session’s transcript by selecting the blue refresh icon. Delete the unsaved session by selecting the red bin icon.</td></tr><tr><td><img src="https://2400606950-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFaQZ82l2KjVefurxtBBp%2Fuploads%2FqckuHD5MqD58NELKNBmV%2Funknown.png?alt=media&amp;token=6b19c1c6-ddef-49d2-ab1d-387b15ffe01d" alt=""></td><td>Session’s transcription process was interrupted. <br><br>Retry the process by selecting the blue refresh icon. Reach out to us if retry doesn't work.</td></tr></tbody></table>

{% hint style="success" %}
Once a recording is **successfully saved** and **has started to process**, you are free to leave the Scribe browser or start a new session. Doing so will not affect the transcript from processing.&#x20;
{% endhint %}

***

### My phone ran out of battery halfway through a session!

Do not panic! You will be able to recover your session as an unsaved recording. Scribe automatically saves your recording **up to the point when your phone battery died**, so you won't lose everything.

**To recover your session:**

1. Refresh your browser
2. You should see your recently saved session show up as an unsaved session<br>

   <figure><img src="https://2400606950-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFaQZ82l2KjVefurxtBBp%2Fuploads%2FiQRaE6B21n3PvT3i7seJ%2FScreenshot%202024-11-26%20at%2010.21.35%20AM.png?alt=media&amp;token=e872a602-747a-4f9e-874a-4f13769a8f92" alt="" width="361"><figcaption></figcaption></figure>
3. Click on ![](https://2400606950-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFaQZ82l2KjVefurxtBBp%2Fuploads%2F9vjZ1HKv9BCAj4YBUpln%2Frevision.png?alt=media\&token=57021682-dd01-471a-8daa-13646c17437d) and re-save your session

**What to expect:** Your recovered session will contain everything that was recorded before your phone died. Any conversation that happened after the battery ran out will not be captured.

{% hint style="info" %}
Unsaved sessions can be recovered **within 7 days of the session date**. After that, they’re permanently deleted and can’t be retrieved.
{% endhint %}

***

If your transcript is still processing after 3 hours, reach out to us via [our support form](https://go.gov.sg/scribe-support) and we'll investigate.


---

# 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/help/my-transcript-is-still-processing.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.