> ## Documentation Index
> Fetch the complete documentation index at: https://docs.jinn.so/llms.txt
> Use this file to discover all available pages before exploring further.

# Check on a recording

> What happens on its own after you stop recording, where the recording lands, and the two moments that need you.

You stop recording and Jinn takes over. The audio is saved, transcribing starts in the
background, and once the transcript is ready the [agents](https://docs.jinn.so/agents/add-an-agent.md) on the project read it and write back
what they found. None of that needs you, and there's nothing to refresh — a recording's page
fills itself in as each part arrives.

You'll find the recording in its [project](https://docs.jinn.so/projects/manage-projects.md), under **Recordings**, newest day first.

## Follow the transcript's progress

Jinn transcribes a meeting in pieces, and its row in a **Recordings** list — in the project, or
on **Home** — shows how far it's got. While the meeting is still recording, the row counts the
pieces done: **1 piece transcribed**, then *2 pieces transcribed* and on. Once you've stopped,
or once an uploaded file is in, Jinn knows how many pieces there are, and the count becomes a
bar that fills up.

The row updates without a reload, and the progress goes once the transcript is ready or has
failed.

Two things do need you: a recording that doesn't belong to a project yet, and a transcription
that failed. Each one shows on the recording and waits in your inbox, and takes a click to sort.

## When a recording has no project

Recording before you've decided where it belongs is the ordinary way to work, not a mistake.
But a recording with no project has no agents on it, and nothing will read the
transcript.

![An inbox notification in Jinn saying a recording needs a project, with a project suggested beside it and Accept next to it](https://mintcdn.com/jinn/48W-8QqP6SyFhGB7/images/meetings/check-a-recording-no-project.png?fit=max\&auto=format\&n=48W-8QqP6SyFhGB7\&q=85\&s=32542e67c6636109fe78b09f709db0f9)

The notification that a recording needs a project

Jinn puts a notification in your inbox and shows the same thing on the recording itself:
*This recording isn't in a project yet.* Pick one, and everything downstream starts by itself
— the agents on that project read the transcript, and the notification resolves.

The transcript is made either way. It's only the analysis that waits.

## When transcription fails

The recording says so where its transcript would be: **Transcription failed**, and a line under
it saying why. If you can edit the recording, **Try again** is there too. Jinn also puts a
notification in the inbox of whoever made the recording, with its own **Try again**. Either
button does the same thing, and a retry carries on from the pieces already transcribed.

| What the message says | What to do |
| - | - |
| **Transcription needs a Gemini key that works.** | The workspace runs on its own keys and the one transcription needs is missing or switched off. Add or fix it in [How your AI is powered](https://docs.jinn.so/workspace/ai-and-indexing.md#key-states-and-what-to-do-about-each), then click **Try again** |
| **The AI provider refused for billing or quota.** | The account behind the workspace's key is out of credit or over its limit. Top it up with the provider — see [How your AI is powered](https://docs.jinn.so/workspace/ai-and-indexing.md#key-states-and-what-to-do-about-each) — then click **Try again** |
| **The AI provider returned an error.** | Click **Try again**. It usually works |
| **Transcription stopped making progress.** | Click **Try again**. It usually works |
| **The recording couldn't be put together on the server.** | Click **Try again**. Jinn finishes saving the audio first, then transcribes it |
| **Something went wrong on our side.** | Click **Try again**. It usually works |

A transcript that came out with a stretch missing hasn't failed — see
[gaps in the transcript](https://docs.jinn.so/meetings/review-a-meeting.md#fill-a-gap-in-the-transcript).

## When an agent fails

A failed agent gets a red warning mark in the row of agents, and the recording says
**Insight generation failed** where its summary would be.

![A recording in Jinn where the Default agent carries a red warning mark and the page reads Insight generation failed, with Try again](https://mintcdn.com/jinn/48W-8QqP6SyFhGB7/images/meetings/generation-failed.png?fit=max\&auto=format\&n=48W-8QqP6SyFhGB7\&q=85\&s=f641553dfa6fe55f32106b4c9cb297b1)

Default couldn't write up the meeting

Click **Try again**. If it keeps failing, the cause is usually the workspace's AI setup rather
than this meeting — on a workspace running on its own keys, a key that has stopped working. See
[How your AI is powered](https://docs.jinn.so/workspace/ai-and-indexing.md).

## Check your inbox

Both of these live in your inbox, and the inbox is per workspace — what's waiting in one
workspace doesn't show up in another. You can mark things read, archive them, or clear the lot
with **Mark all as read** and **Archive all**.

Notifications about a recording resolve themselves once the thing they're about is sorted.
Assign the project and the notification goes; the transcription succeeds on a retry and the
failure notice becomes a success.

## Download the audio

Need the recording outside Jinn — to send to someone who wasn't there, or to keep a copy of
your own? Click **Download recording** on the recording's player, or choose it from the **⋯**
menu at the top of the recording's page or on its row in a **Recordings** list. The file is
named after the meeting.

Anyone who can open the recording can download it.

## What to do with it next

Once the transcript and the agents' write-ups are there, the meeting is yours to work on. What
you do with it while you still remember the room decides whether it's any use later — see
[the five minutes afterwards](https://docs.jinn.so/meetings/put-a-meeting-to-work.md). Every control on the
recording's page is in [reviewing a meeting](https://docs.jinn.so/meetings/review-a-meeting.md).

## Where to go next

> [card] [Upload a recording](https://docs.jinn.so/meetings/upload-a-recording.md)
>
> Turn an audio or video file you already have into a meeting.

> [card] [Put a meeting to work](https://docs.jinn.so/meetings/put-a-meeting-to-work.md)
>
> The five minutes that decide whether a meeting is worth anything later.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.