Stop a generation and get your credits back
Cancel is a real first-class action. Vendor stops, credits refund, your library updates — all in one transaction.
Hit submit, watch the queue, realise you misspelled the subject. What happens when you click Cancel?
The cancel button is wired to a real backend endpoint, not a client-side hide. It calls the vendor to stop the inference if it’s still running, writes the generation row to cancelled, and posts a refund line to your credit ledger — all in one database transaction. So either the cancel succeeds and your balance is whole again, or it doesn’t and nothing changed.
Two practical notes. First: if the worker has already received the vendor’s final output, cancel is too late — the generation is succeeded, the credits stay spent, but you have the result. Second: cancelling a queued (not-yet-started) generation refunds you instantly because there’s nothing to undo on the vendor side.
You can cancel from the studio output rail or from any Library row that’s still queued or running.