Generation stuck or failed?
Immediate resolution steps, common error causes, and our automatic credit refund policy.
While Socialshot maintains 99.8% inference reliability, hardware spikes, network disconnects, or unsupported file formats can occasionally interrupt a generation. Here is how our automated safeguards protect your credits and how to get back on track.
Zero Lost Credits
Why Generations Might Stall or Fail
The most common reasons for a generation delay or failure include:
- File size exceeding 25MB: Extremely high-res RAW camera files should be compressed to JPEG or WebP before uploading.
- Network interruption: If your browser drops connection while streaming the generation progress websocket, the job may fail safely.
- GPU Queue Surge: During peak usage, our autoscaler spins up extra GPU nodes. If a cold-start timeout occurs, the job cancels and auto-refunds.
The Auto-Refund Guarantee
Whenever a generation job encounters an error or reaches the 60-second execution ceiling, our backend automatically executes an atomic refund to your credit balance. A toast notification will confirm: 'Generation was not completed. Your credits have been refunded.'
Step-by-Step Fixes for Common Issues
- Hard Refresh: Press
⌘Shift+R(orCtrl+Shift+R) to clear cached client bundles. - Re-upload file: Ensure your source image is under 20MB and in PNG, JPG, or WebP format.
- Switch aspect ratio: If out-of-memory errors persist on a massive image, select a standard 1:1 or 4:5 ratio.
Contacting Engineering Support
If an issue persists across multiple tools, please submit a ticket via the Contact Page (/contact) or reach out in the Community Support channel. Include your generation ID from your generation history for immediate triage.
Was this page helpful?
Your feedback directly shapes our documentation and guides.