Troubleshooting and failure modes
What common errors mean and what to do about each one.
Last updated · September 2026
On this page
Most problems surface as one of the messages below. Each one tells you whether to retry, reconfigure, or ask for help.
Authentication required.
Sign in again. In production, workspace requests require a valid signed session.
Insufficient token balance.
Shorten the prompt or evidence, or add balance through the pricing page. The request is rejected before inference.
The analysis stream was unavailable.
The upstream response did not provide a readable body. Check provider health and server logs.
The response stops partway through.
Treat the investigation as incomplete unless a done event was received. Retry with the same case reference and note the interruption.
Rampart returns no findings.
The code may be clean, or the repository read failed partway. Check the scan status on the repository page and retry; private repos need a connected GitHub account.
My reset link does not work.
Links expire after 30 minutes and work once. Request a fresh link from the sign-in page.