Generations that appear slow or "stuck" are usually a queue delay, a browser rendering issue, or a temporary service disruption — rarely a lost job. This guide walks through how to tell the difference and what to check first.

A generation that shows a spinner for longer than expected is still processing in the vast majority of cases. Complex prompts, high concurrency, and larger models can all extend processing time well beyond the typical duration.

Before assuming something failed, wait a few extra minutes — refreshing or navigating away does not cancel the underlying job, and the model will still appear in your assets once complete. If you refresh, revisit "My Assets" rather than restarting the generation to avoid using extra credits.

If the 3D viewer itself feels laggy or unresponsive (rather than the generation being slow), this is typically a local rendering issue. Try a hardware-accelerated browser, close other GPU-intensive tabs, or reduce the model's polygon/texture preview settings — see the viewer-lag article linked below for details.

During peak usage, generations may queue behind other jobs on your plan's concurrency limit. Higher-tier plans generally have higher concurrent generation limits, which can reduce queue wait times.

If you're generating via the API, poll the task status endpoint for your task ID rather than assuming failure from a client-side timeout — the task may still be marked "IN_PROGRESS" on Meshy's servers even if your request timed out locally.

If many generations across your account seem delayed at once, check Meshy's public status page for any active incident before contacting support — this is the fastest way to confirm whether a slowdown is on our end.

Complex prompts and busy periods can extend generation time. Give it additional time before canceling, since canceling and retrying still uses credits.

See the linked article on generation failures below for how credit deduction works in failure cases.

This is a local rendering issue, not a generation delay. See the browser viewer troubleshooting article linked below.