---
title: Troubleshooting
description: What to do when a session stops, a check fails for reasons unrelated to your change, a preview won't start, or the API refuses a request.
---

## Sessions

??? question "A session stopped and says it needs me, but nothing is wrong"
    Open the session and read the **Awaiting you** reason. The most common is a
    budget stop: the session reached its limit. Extend the budget from the
    session, or raise the account budget under **Wallet & usage**.

??? question "A check fails that has nothing to do with my change"
    That is a **pre-existing failure**: it was already failing before the session
    started. Ysra reports it separately and doesn't count it against the change.
    Fix it on your default branch, or mention it in the goal if you want Ysra to
    fix it too.

??? question "The session keeps hitting the same failure and stops"
    When the same outcome repeats with no progress, Ysra stops rather than loop.
    The last failure usually points to something outside the code — a service,
    test data or a setting the tests expect. Steer the session with that
    information and continue.

??? question "Everything passed, but criteria show as unproven"
    Your checks passed, but some requirements describe behaviour that has to be
    exercised in a browser, and browser review wasn't enabled. Ysra reports those
    as *unproven*, not passed. Start a follow-up with browser review turned on.
    See [Evidence and verification](../developer/review.md).

??? question "Ysra asks before installing a package"
    That is `package_installs: ask` in your
    [autonomy policy](../workspace/autonomy-policy.md). Approve it once in the
    session, or allow installs for that repository if the answer will always be
    yes.

## Previews

??? failure "The preview takes a long time to open"
    The first preview installs dependencies, builds and starts the application
    from a clean copy, so it can take a few minutes for larger projects. Later
    previews of the same version are faster.

??? failure "The preview opens but the app asks me to sign in"
    If the application needs an account, the preview offers temporary sign-in
    details created for that preview only. Use those rather than real
    credentials.

## API

??? failure "Every request returns 401"
    The token expired (tokens last 24 hours by default) or the account was
    deactivated. Sign in again with
    [`POST /auth/login`](../api/authentication.md).

??? failure "Saving the policy or budget returns 409"
    Someone else saved first, or `expected_version` was left out after the first
    write. Refetch, show the current values, and submit again with the new
    `version`. See [Errors](../api/errors.md).

??? failure "Requests fail with 503"
    The execution account is briefly unavailable. Retry with exponential backoff;
    mutations that carry an idempotency key are safe to resend with the same key.

## Still stuck?

Contact us with the session link. Session reports include the evidence we need,
so you won't have to reproduce the problem.