A run will not start
Choose a plan and add a card to start your trial
Choose a plan and add a card to start your trial
The account has never subscribed. Runs need a plan with a card on file;
every plan starts with a 3-day trial. Pick one on the pricing page. See
Plans and limits.
Runs are paused on this account
Runs are paused on this account
The plan has ended, the subscription is unpaid or paused, or a payment
has been past due for more than 72 hours. Update your card or choose a
plan. Projects and recent history stay readable meanwhile.
Your allowance is used up
Your allowance is used up
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 add runs and minutes, not AI
allowance. During a trial, the refusal names the day the plan starts.
All of your plan's runs are in use
All of your plan's runs are in use
Your plan’s concurrent-run limit, counted across all its workspaces. The
chat lists what is running. Wait for one to finish and press Try
again, or stop one. The API answers
429 with concurrency_limit.Every test browser is busy
Every test browser is busy
The service’s capacity, not your account. The run waited in line and no
browser freed up in time (3 minutes at the front, or 10 minutes in line).
Press Try again in a moment.
This feature needs a subscription
This feature needs a subscription
Form fuzzing and the role probe are refused on an account with no
subscription, because one fuzz click fires many runs. They are gated in
the service, not just in the UI. A trial counts as a subscription.
A plan would open another site
A plan would open another site
The planner wrote a step that navigates to a host neither the project nor
you named, and the run was refused before it started. If you meant that
site, name it in the instruction.
Too many tabs are open
Every signed-in tab holds a live connection, up to 12 per person. Beyond that the chat says too many tabs are open and stops reconnecting. Close a few and press Reconnect.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.
A name that does not resolve at all is not blocked: the navigate step fails
saying the host does not resolve. Check the spelling.
The test signed in, then the next step acted as a stranger
Set the procedure’s auth mode. A sign-in test needs “Fresh logged-out each leg”; a dashboard test needs “Reuse saved login state”. If the saved login has expired, re-run the login-setup procedure.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 click that changed neither the address nor anything on the page passes with a warning saying so. Read it; an overlay may have taken the click. If the page genuinely responds in place (a toast, an inline error, a removed row) that counts as a reaction and there is no warning.A replay refused to run against my preview
A procedure holding a saved password types it only on the project’s own address, one of its environments, or the linked repository’s pull request preview. Add the host as an environment and run against that.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. The screenshot and the recordedactual value
are the ground truth.