←View full Viggle status
Viggle: Rendering Stuck / Processing Timeout
Current Status: Degraded
Last checked: 7m ago
What We're Seeing Right Now
No recent issues reported. If you're experiencing problems with Viggle, report below to help the community.
What is this error?
When Viggle video rendering gets stuck, the progress bar stops moving or the processing time far exceeds the expected duration. This is common during peak usage when GPU resources are constrained.
Error Signatures
Stuck at 99%Processing...Rendering in progressStill processingTaking longer than expectedJob queuedEstimated time remaining: unknownProcessing timeoutCommon Causes
- GPU queue is backed up — your job is waiting
- The rendering process crashed silently
- Complex scene or long duration causing timeout
- Server-side error that didn't report back properly
- Viggle is experiencing high demand
✓ How to Fix It
- Wait up to 15-30 minutes before assuming it's stuck
- Check this page for reports of widespread slowness
- Cancel and resubmit the job if possible
- Try a shorter or simpler generation
- Clear your browser and try fresh
- Contact Viggle support if credits were consumed without output
Live Signals
Service Components
Viggle Web
Checking...Recent Incidents
No incidents in the past 30 days
Frequently Asked Questions
Why is Viggle rendering stuck?
Video rendering is GPU-heavy. During peak times, jobs queue up. If stuck for 30+ minutes with no progress, cancel and retry.
How long should Viggle video rendering take?
Typically 2-15 minutes depending on length and complexity. Anything over 30 minutes likely means an issue.
Will I lose credits if Viggle rendering fails?
Policies vary. Check Viggle's terms — most services refund credits for failed generations.