Generation interrupted

When a response can't complete, the chat keeps whatever was produced and marks it (generation interrupted: …). Nothing is written to your project. Here is what the reasons mean.

"The model stopped responding: no data for 90s mid-stream"

The provider stopped sending tokens for a minute and a half. This is a provider-side stall, not a limit on your side. Send the prompt again — often a different provider route is used. If it repeats on one model, try another from the picker.

"The model stopped responding: no response for 180s after the request was sent"

The provider accepted the request but never started answering. Same remedy: retry, or switch model. The status page shows whether the model gateway is having a wider problem.

"Generation cancelled"

You clicked Stop.

The answer ended mid-file

This should be rare: when a model reaches its output limit, Qyant asks it to continue from exactly where it stopped, up to four times, and stitches the result. If a change set still arrives incomplete, the review will show the truncated file — reject it and re-prompt with a smaller scope ("just the API route first").

"Monthly credit limit reached" / "AI allowance used up"

You've used this month's credits or allowance. See Plans & credits; upgrading lifts the limit immediately.

Timeouts are never about length

A healthy generation is never cut off for taking long — long multi-file changes can run for many minutes. Only silence from the provider ends a request early.