Meetings
When a meeting gets stuck
The difference between slow and wedged, and what the system fixes on its own.
Last updated 1 min readFor team members
Three common states
The meeting has said "processing" for hours
- What it means
- The job that was splitting or transcribing stopped half-way.
- What to do
- Nothing to do — a periodic sweep finds this state and marks genuinely stalled segments as failed, which is what turns on your retry button.
It says "already being processed" but nothing progresses
- What it means
- The split job never ran and left its claim behind.
- What to do
- The same sweep re-runs the split and the segments arrive in a retryable state. Wait one cycle and refresh.
One segment failed while the rest are fine
- What it means
- A transient error from the transcription service — a rate limit, a timeout, or a temporary fault.
- What to do
- Hit retry. Only that segment runs; the segments already transcribed are untouched.
Slow is not stuck
A meeting that is still making progress is left alone, however long it is taking. The test is whether progress is happening at all, not how long it has been running.
So the sweep leaves a slow but living meeting alone and only goes after what has genuinely stopped.
Read this next
Still stuck?
If the answer wasn't here, write to us. It is a real inbox and it gets answered.