You submit a generation, the progress shows 0%, and 30 minutes later it’s still 0%. Or it sits at 5% indefinitely. The platform doesn’t error out — it just hangs. Meanwhile you’re burning the time you set aside for the work.
Most AI video platforms (Runway, Pika, Kling, Luma) have queue systems shared across all users. During peak hours, free tiers can wait hours; paid tiers minutes. But sometimes a job gets truly stuck — and you need to cancel and resubmit rather than wait.
Common causes
Ordered by hit rate, highest first.
1. Free-tier peak-hour queueing
US daytime and EU evening hours are peak. Free tier wait can balloon to hours.
How to spot it: it’s a peak hour in major markets; you’re on free tier. Status is “queued” not “processing.”
2. Account concurrency cap saturated
Most plans cap concurrent jobs (e.g., 2 at once on standard, 5 on pro). If you already have 5 running, the 6th queues until one finishes.
How to spot it: check the dashboard. Multiple jobs in “running” state, new one stuck.
3. Previous job hung server-side and hasn’t released quota
Sometimes a previous job hangs (stuck at 50% indefinitely). It’s still occupying your concurrency slot. New jobs queue behind it.
How to spot it: a previous job has been “running” >1 hour without progress.
4. Tool experiencing platform-wide issue
The platform has a backend bottleneck or outage. Twitter / their status page will confirm.
How to spot it: check the platform’s status page, X/Twitter, or community Discord.
5. Job exceeds tier limits (silent reject)
You requested a 10s clip but your tier only supports 5s. Platform may queue it forever waiting for tier upgrade instead of error.
How to spot it: clip duration, resolution, or quality exceeds your tier’s documented limits.
6. Browser tab issue (job actually progressing)
Your browser tab is asleep, websocket disconnected, but the job is actually running on server. Refresh shows it’s done.
How to spot it: refresh / hard-reload the page. Job may show as completed.
Shortest path to fix
Step 1: Refresh the page first
The simplest fix: your browser tab may have disconnected from the live status updates.
1. Hard refresh (Cmd+Shift+R / Ctrl+Shift+R)
2. Check if the job actually completed
3. If still queued, proceed to Step 2Step 2: Cancel stuck jobs
If a job has been “running” >30 min with no progress:
# Per platform
- Runway: Dashboard → click job → "Cancel"
- Pika: My Generations → click job → "Cancel"
- Kling: AI Video → My Tasks → Cancel
- Luma: Dashboard → menu → CancelCancellation usually refunds credits (check terms).
Step 3: Submit at off-peak UTC hours
Peak / off-peak guide:
# Peak (avoid)
- US daytime: 14:00-22:00 UTC
- EU evening: 18:00-22:00 UTC
- Asia evening: 12:00-15:00 UTC
# Off-peak (best queue times)
- 02:00-08:00 UTC (early morning UTC = night in US, morning in Asia)
- Weekends are sometimes lighterStep 4: Check status page
# Status pages
- Runway: status.runwayml.com
- Pika: discord (no formal status page)
- Kling: check Twitter @Kling_ai
- Luma: status.lumalabs.ai
# Also check
- Reddit r/AIVideo or r/MidJourney for current outage reports
- X/Twitter search "[tool name] down"Step 5: Verify your job fits tier limits
# Check before resubmitting
- Duration: within tier limit?
- Resolution: 720p / 1080p supported?
- Mode: free tier may exclude "premium" or "pro" mode
- Special features (extend, image-to-video) may be tier-gatedStep 6: Upgrade tier or fall back to alternate platform
# Quick fallback
- Runway stuck → try Kling or Pika for the same shot
- Kling stuck → try Hailuo (often less loaded)
- All stuck → wait 2-4 hours and retry
# Long-term
- Pro tier on most platforms is $50-100/mo
- Buys you concurrency, queue priority, longer durationsPrevention
- Submit during off-peak UTC hours when you have flexibility
- Don’t queue more than 1-2 jobs at once; wait for completion before next batch
- Keep accounts on 2 alternate platforms so you have a fallback when one queues up
- For deadline work, schedule generation the day before, not the morning of