Clip asset stuck processing – no download URL
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 88
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
**Describe the bug (required)**
We are creating clips from a Livepeer live stream using the API.
The clip request succeeds and returns an asset ID, but some assets do not appear to complete processing and a usable download URL never becomes available.
The live stream itself is working correctly.
Example affected asset:
- Playback ID: `2f2du0wurortk6zn`
- Asset ID: `2f2d2bff-55ca-42ab-afe6-8894090240d0`
- Clip created: August 27, 2026 at approximately 9:34 PM
- Livepeer Studio plan: Growth
When viewing the affected asset in Livepeer Studio, the Events Log also does not appear to load/display any information.
**Expected behavior (required)**
After creating a clip, I expect the asset to finish processing and provide a download URL that can be used to retrieve the generated video file.
**To Reproduce (required)**
1. Start a live stream in Livepeer.
2. Create a clip from the stream using the Livepeer API.
3. Receive the asset ID from the successful clip request.
4. Poll/retrieve the asset using the API.
5. Wait for the asset to finish processing.
6. No usable download URL becomes available for the affected asset.
7. Open the asset in Livepeer Studio and view the Events Log.
8. The Events Log does not appear to display any information.
**Device (required):**
- Device: MacBook Pro
- OS: macOS
- Browser: Google Chrome v151.0.7922.172
**Screenshots (optional)**
**Additional context (optional)**
Our workflow is:
Live stream → Livepeer → create clip via API → wait for asset processing → retrieve/download asset → process with FFmpeg.
Live streaming is functioning normally. The issue appears specifically related to clip/asset processing and retrieval.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No repository file, entry point, or test is identified; start by reproducing the API clip workflow with asset ID 2f2d2bff-55ca-42ab-afe6-8894090240d0 and inspect asset processing and the Studio Events Log. Done means affected clips complete processing, expose a usable download URL, and show event information in Studio.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, audio-video-rtc, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100