Help
Common problems, and how to get an answer from a person.
A step cannot find its element
The selector no longer matches. Open the step, press the picker, and point at the control again — Cettara checks the new selector against the live page before it offers it. If the element only appears sometimes, add a Wait before the step.
A run timed out
A timeout is not a failed expectation: nothing was judged. Usually something never arrived. Add a wait for the thing you are actually waiting for, or raise that step's limit under More options. The project-wide limit is in Settings → Thresholds.
The sign-in block did not carry over
Mark it run once, so every case in the run shares the session. If the app signs you out between cases, check that the environment's URL matches the one the session was issued for.
A checkpoint failed but the screen looked right
Read the reasoning and the evidence it named. The two common causes are an expectation that describes something the screen never shows, and a page whose text the run could not extract. If the judge is simply wrong, Disagree and say why: that correction teaches it for next time and is counted on the Trust page.
A download was not kept
Only certain file types are kept, and only up to the size limit and your organization's storage. The run page says which of those stopped it.
We ran out of AI credits
Each plan includes an allowance each month; more are two cents each under Organization → Billing. Manual testing never spends credits.
Ask a person
Write to us from the contact form, or email [email protected]. If it is about a specific run, the run's number and the project name are enough for us to find it.