Stopping a run

While a run is in progress, a Stop button is available. Stopping is ownership-checked — only the account (or, for an anonymous run, the same browser fingerprint) that started the run can cancel it.

Do you get your credit back?

Yes — stopping a run refunds the credit, the same as any other run failure. This is a deliberate policy: an incomplete run shouldn't cost you.

There is a daily cap (10 per account by default) on how many Stop-triggered refunds one account can receive — a guard against someone repeatedly starting and immediately canceling runs to abuse the free/low-cost tiers. Past that cap, the cancel itself still succeeds (the run stops), but the credit is not returned. In ordinary use — stopping a run because you changed your mind or made a mistake — you will never come close to this limit.

What if the deep analysis already finished?

Once the expensive part of a run (the deep analysis) has actually landed, Stop still works but is understood as canceling the rest of the pipeline (verification and assembly), not undoing work that already happened — the refund logic accounts for this rather than assuming every stop is equally cheap.

Runs that fail on their own

Every failure path — a timeout, a provider outage, an unusable model output, or a stalled run rescued by the platform's own recovery sweep — refunds the credit automatically, exactly like a manual stop. You'll see one of a small set of error codes (SMX-E01–SMX-E05) with a plain-language explanation; none of them expose internal details like which model or provider was involved.

Every one of these except SMX-E06 returns your credit.