# Running and submitting

> What Run checks and what Submit checks, how to try your own input, what gets kept, and what the daily allowance actually limits.

Source: https://www.revquix.com/docs/practice/running-and-submitting
Last verified: 2026-09-04

---

Two buttons, and the difference between them is what gets kept.

|                                            | **Run**                                | **Submit**                       |
| ------------------------------------------ | -------------------------------------- | -------------------------------- |
| Which cases                                | the worked examples, or your own input | every case, hidden ones included |
| Needs an account                           | no                                     | yes                              |
| Recorded                                   | no                                     | yes, permanently                 |
| Counts toward your solved total and streak | no                                     | yes                              |
| Shows the expected output                  | yes - the examples are public          | only for the first failing case  |

Run is for checking your thinking. Submit is the one that decides whether the problem is solved.

## Trying your own input

The Testcase pane starts prefilled with whichever example is selected, one field per parameter.
**Edit any of them and the next Run uses your values instead of the example's.**

Each field holds a JSON value - `[2,7,11,15]`, `"abc"`, `9`. There is a reset control to put the
example's values back.

> **Note** - A custom run is not graded, and says so
>
> There is no expected answer for input you invented, so a custom run reports **Finished** and shows
> what your function returned. It never says Accepted - a green tick on a run that compared nothing
> would be a claim about correctness we have not made.

## Running without an account

Run works signed out. You may be asked to complete a quick "are you human" check the first time,
which is there to keep the sandbox available for everyone rather than to slow you down.

Submit needs an account. The button is still there when you are signed out - it reads **Sign in to
submit**, and your code is still in the editor when you come back.

## What a submission keeps

Every submission stores the source you sent, the verdict, which case failed if one did, the runtime
and memory, and the timestamp. All of it is readable later from the Submissions tab and from [your practice dashboard](https://www.revquix.com/dashboard/practice).

Storing the source in full is the point rather than a side effect - it is what makes your own
earlier attempt available to you months later.

> **Note** - Double-clicking Submit does not submit twice
>
> Each attempt carries a key, so a double press or a retry over a flaky connection lands as one
> submission and one entry on your activity graph.

## The daily allowance

Runs and submissions draw on a daily allowance shared with the Playground and with Projects runs. It
is generous enough that ordinary practice never reaches it, so it is shown **only once you are close
to it** - "7 runs left today" appears beside the buttons rather than sitting there all day.

Signed-out runs get a smaller allowance than signed-in ones. There are also per-minute limits: Run
is capped well above any human typing speed, and Submit is tighter, because a submission runs every
case and holds a sandbox slot for longer.

If you do hit a limit, the message says so plainly. It is not a fault in your code.

> **Warning** - If the runner says it is busy, wait a moment and press Run again
>
> The sandbox runs a small number of jobs at once, and it fails fast rather than queueing you behind
> four other people's compiles. A fifteen-second Run button reads as broken; a quick "busy" is honest.

## Related

- [Verdicts and test cases](https://www.revquix.com/docs/practice/verdicts-and-test-cases) - What each result means.

- [Languages and limits](https://www.revquix.com/docs/practice/languages-and-limits) - The time and size ceilings your code runs under.