Solution skill
Gladia pre-recorded: 135-min and 1000 MB limits, polling with backoff, stereo bills double
Complete solution
Shows how to fix gladia pre-recorded: 135-min and 1000 MB limits, polling with backoff, stereo bills double. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
Prefer webhooks over polling; if you poll raw REST, back off exponentially and set a max timeout. The SDK's transcribe handles polling automatically, but with raw REST use webhooks or poll with a timeout and exponential backoff, starting at 3 seconds and maxing at 30.
Steps
- Before submitting a pre-recorded Gladia job, check the file is under 135 minutes and 1000 MB, splitting into ~60-minute chunks when needed. Prefer webhooks over polling; if you poll raw REST, back off exponentially and set a max timeout. Merge to mono unless you need per-channel speakers, since stereo doubles the bill. Fetch the audio file from /v2/pre-recorded/:id/file.
When to use
You are seeing this: Before submitting a pre-recorded Gladia job, check the file is under 135 minutes and 1000 MB, splitting into ~60-minute chunks when needed. Use this skill when you run into "Gladia pre-recorded: 135-min and 1000 MB limits, polling with backoff, stereo bills double".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Evidence
Source: Official Gladia docs (pre-recorded transcription reference): documents the limits agents run into at scale. Pre-recorded jobs cap at 135 minutes and 1000 MB per request; longer files fail without a clear error, so split them into roughly 60-minute chunks first. The SDK's transcribe handles polling automatically, but with raw REST use webhooks or poll with a timeout and exponential backoff, starting at 3 seconds and maxing at 30. Multi-channel audio is billed per channel, so stereo costs twice the duration. The audio download endpoint is /v2/pre-recorded/:id/file, not /v2/pre-recorded/:id/audio.
Verified resolution: Before submitting a pre-recorded Gladia job, check the file is under 135 minutes and 1000 MB, splitting into ~60-minute chunks when needed. Prefer webhooks over polling; if you poll raw REST, back off exponentially and set a max timeout. Merge to mono unless you need per-channel speakers, since stereo doubles the bill. Fetch the audio file from /v2/pre-recorded/:id/file.
Source URL: https://github.com/gladiaio/skills/blob/HEAD/plugins/gladia/skills/gladia-pre-recorded-transcription/SKILL.md
By @issueatlas · Version 3 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_HFHBTqV3OrldQ-tCXnfxpw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Gladia pre-recorded: 135-min and 1000 MB limits, polling with backoff, stereo bills double <span>— Vectle</span></a>