”My test was abandoned”
A test abandons when the agent decides it can’t complete the scenario. Common causes:- Three consecutive failed actions. The agent tried to do something three times in a row without success.
- Stuck below 50% progress after 15 steps. A safety net to stop drifting runs.
- Hit the step ceiling. Default 50 in the agent; the web app has its own cap.
- Check the flow timeline — the last few steps usually show what tripped the agent up.
- Dismiss cookie banners / modals in the scenario. Include “dismiss any cookie banners that appear” explicitly if they’re blocking.
- Sharpen the scenario. “Buy something” is too vague; “Add a specific product from the running shoes category to the cart” is testable. See Writing good scenarios.
”Percio can’t reach my URL”
The web app’s browser runs on our servers and needs network access to your URL.- Authentication walls. If the URL requires sign-in, the agent can’t get past it. Either test signed-out flows, or use a staging environment with the auth removed.
- Staging / internal URLs. If the URL is only reachable from inside your company network, Percio can’t see it. Use the agent CLI to run the test from your own machine.
localhost. The web app can’t reach your local machine. Use the CLI:percio test --url http://localhost:3000 --flow "...".- IP allowlists. If your staging environment allowlists specific IPs, Percio’s server IP needs to be on the list.
”I ran out of credits mid-month”
Credits reset at the start of each billing cycle. Options:- Upgrade to Pro for a higher monthly allotment.
- Wait for the reset. Your Billing page shows when the next reset happens.
- Be more selective. Only rerun a scenario when you’ve changed something — a fix, a different persona, a tightened scenario. Repeating the same run on the same build rarely produces new insight.
”Results don’t match what I expected”
Almost always a scenario problem. Read Writing good scenarios. Quick checks:- Is the scenario specific enough? Generic scenarios produce generic reports.
- Did the right persona run the test? A first-timer’s report will differ sharply from a power user’s.
- Did the agent actually test what you wanted? The flow timeline shows exactly what the browser did. If it never reached the feature you care about, the scenario needs to steer it more directly.
”I can’t find an old test”
Test results age out of retention:- Indie — 90 days
- Pro — 365 days
”A persona keeps raising false positives”
Tune the persona. On the Personas page, open the persona and adjust:- Focus areas — too broad? Narrow them.
- Pain points — are they accurate for this segment, or generic?
- Behavioral traits — does the persona react the way you’d expect this user to react?
”I accidentally deleted a persona”
Personas can’t be recovered after deletion. Past test results that used the persona are still viewable (the persona’s details are captured in the report). To keep something similar going forward, recreate it — the creation flow is quick.”I forgot my password”
Use the Forgot password link on the sign-in page. A reset email goes to your account’s address. If you signed up with Google, you don’t have a password — use Google sign-in. You can optionally set a password from Settings if you want email + password as an alternative.Where to get help
- Check Core concepts if the terminology is the confusion.
- Check Agent troubleshooting for CLI or MCP issues.
- Contact Percio support for anything else, with your test id or the specific error you’re seeing.