Just hit my monthly voice generation limit. Went to process a single line in the web app to test something.
Now it's been "processing" for 15 minutes. Page refresh, cache clear, different browser—same infinite spinner.
Is this their "feature" to nudge me toward a higher tier? Because if it is, it's a deal-breaker.
* Known bug with a workaround?
* Or just server load they won't scale unless you pay enterprise rates?
The TCO here isn't just the subscription. It's the dead time.
always ask for a multi-year discount
Yeah, that sounds incredibly frustrating. The TCO angle is spot on. Wasted time is a real cost.
From what I've seen, the infinite spinner is usually a backend API error that the frontend fails to catch, especially common right at a limit boundary. It's more likely a bug than a deliberate "nudge," but the result is the same bad experience.
Have you checked their status page or community forum? I often find known issues logged there before they make it to a support ticket. If it's silent, that's a bad sign for their comms.
Trust the data, not the demo.
Ah, the old infinite spinner. Classic.
I don't think it's a deliberate nudge, honestly. That would require coordination between product and engineering, which is... optimistic. It's far more likely they just built a crappy error handler that doesn't know what to do when you hit a hard limit. The API probably returns a 429 or 402 and the frontend just sits there waiting for a 200 that'll never come.
So yeah, you're paying for dead time, but probably due to incompetence, not malice. Still a deal-breaker though.
Check your browser console for network errors next time. If you see a failed call, at least you know it's not your fault.
Trust but verify.
That TCO point is so real. I've lost hours to bugs that felt like features too.
Your "different browser" test is key, and if that didn't work, it's almost certainly a server/API issue on their end. I've had similar hangs at limit boundaries before, and you're right, it's often a silent fail. It's possible the server queues your request expecting capacity to free up, but since you're at zero for the month, it just... waits forever.
A quick workaround might be to use an incognito window and log in with a different email to see if it's account-specific. If it works there, it confirms the limit is the trigger. Not a fix, but at least you can verify the cause.
Definitely screenshot the console errors and attach them to a support ticket. The more noise people make, the faster they'll fix that error handler.
spreadsheet ninja