Hi everyone, I'm pretty new to Opus Clip and have been using it for the last week to process my team's product demo videos. I've been loving the results when it works!
But I've hit a snag on my last two attempts. I uploaded a 25-minute MP4 (about 1.2GB) and it's been stuck on the 'Analyzing' stage for over 5 hours now. The first few videos I did last week went through this stage in maybe 15-20 minutes tops.
Here's what I've already tried, based on skimming some older threads:
* Refreshed the page and logged out/in.
* Tried from a different browser (Chrome to Firefox).
* Made sure the file format/codec is the same as my successful uploads (H.264, AAC audio).
The video content isn't unusual—it's a standard screen recording with webcam overlay, similar to my previous ones. No crazy graphics or anything.
Is there a known backend queue or something that can cause this? Or does file size become a bottleneck at a certain point? I'm hesitant to cancel and re-upload because the original processing time is a sunk cost now 😅
From a product analytics angle, I'm super curious: does the "Analyzing" stage typically have a timeout or a retry logic that users can trigger? Or are we just at the mercy of the queue?
Ugh, I feel this. Had a similar thing happen with a 18-min file last Thursday. Refreshing didn't help me either.
What finally worked for me was just leaving it overnight. Woke up and it was done, but the status never updated until I hard-refreshed the page (ctrl+F5). Maybe their status updates get stuck?
Is there a dashboard page that shows your clip history? I saw a "processed" timestamp there for my stuck one that didn't match the job page at all.
Learning the ropes
That's a really interesting observation about the dashboard timestamps not matching. I've noticed similar async job state mismatches in other video processing pipelines I've benchmarked. The UI is often polling or receiving webhook updates from a separate queue system, and those can desync under heavy load.
Your hard-refresh fix points to a frontend state caching issue, not necessarily a backend processing stall. It would be useful to check the browser's developer console network tab for the status-polling API calls next time. If they're returning 200 with a "completed" status while the UI still shows "Analyzing", that confirms the bug is purely in the client-side state management.
Leaving it overnight is a valid workaround, but it does make proper incident triage and user trust difficult if the UI isn't reliable.
—chris