> ## Documentation Index
> Fetch the complete documentation index at: https://docs.testorim.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Common issues

> The problems people actually hit, and what to do about each.

## A run will not start

<AccordionGroup>
  <Accordion title="Choose a plan and add a card to start" icon="credit-card">
    The account has never subscribed. Runs need a plan with a card on file.
    Pick one on the [pricing page](https://testorim.com/pricing).
  </Accordion>

  <Accordion title="You have used this period's allowance" icon="gauge">
    Runs, browser minutes, or the AI execution allowance included with the plan
    are spent for the current billing period. Wait for the reset, upgrade, or
    buy a credit pack. Credit packs extend runs and minutes, not the AI
    allowance.
  </Accordion>

  <Accordion title="Too many runs already in flight" icon="layers">
    Your plan's concurrent-run limit. Wait for one to finish, or cancel one
    from the active-runs toast.
  </Accordion>

  <Accordion title="This feature needs a paid plan" icon="lock">
    Form fuzzing and the role probe are paid features, because one fuzz click can
    spend a trial's entire allowance, so they are gated in the service, not
    just in the UI.
  </Accordion>

  <Accordion title="Testorim is temporarily busy" icon="server">
    The global capacity cap, not your account. Retry shortly.
  </Accordion>
</AccordionGroup>

## The address was refused

Private and internal hosts are blocked: `localhost`, loopback, RFC1918 ranges,
link-local and cloud metadata endpoints, in IPv4 and IPv6 form. Expose a local
build through a tunnel and use the public URL.

## The test signed in, then the next step acted as a stranger

Set the saved test's [auth mode](/test-creation/reusable-flows#login-and-auth-mode).
A sign-in test needs `fresh_logged_out`; a dashboard test needs
`reuse_login_state`. If the saved login state has expired, re-run the
login-setup test.

## The sign-in form has two screens and the test only filled one

This is handled for you in both directions. If the plan skipped the
intermediate **Continue** click, it is clicked; if the plan included one on a
single-screen form, it is skipped with a warning. If it still fails, name the
intermediate step explicitly in the instruction.

## A step passed but nothing happened

You will see a warning: a submit-like click that changed neither the address
nor the visible text is reported and fails the run. If the page genuinely
responds in place (a toast, an inline error, a removed row) that counts as a
reaction and the step is fine.

## The report blamed my site and the screenshot disagrees

That is a bug in Testorim, not a judgement call. Send us the run id. See
[Support](/resources/support). The screenshot and the recorded `actual` value
are the ground truth.

## A check I asked for never ran

The run says so: an unmet request becomes a visible skipped step, and the run
does not pass. Usually the plan hit its 40-step ceiling, so split the test, or
the check is outside what a browser can observe.

## I cannot invite someone

Seats are counted **per account across every workspace you own**, not per
workspace, and open invitations count against them. The refusal names the
numbers. Remove someone, revoke a pending invitation, or upgrade.

## I cannot change a role

Nobody grants, changes or removes a rank above their own, and the last owner
can never be demoted or removed. Admins can manage members and admins, not
owners.


## Related topics

- [Support](/resources/support.md)
- [Create your first test](/getting-started/first-test.md)
- [Debugging a failed run](/test-execution/debugging.md)
- [Reliability](/troubleshooting/reliability.md)
- [Mint a new API key (browser session only)](/api-reference/api-keys/mint-a-new-api-key-browser-session-only.md)