Find the symptom or the exact message you see — in Code threads, previews, the cloud, Ask, public colleagues, routines, credits, integrations, sign-in, the command line or Set up with Ysra — with why it happens and what to do.

On this page

Find the message you see, or your symptom, in the table below, then follow the link to what to do. For the desktop app itself (a window that stays empty, blocked commands, Docker), see Desktop troubleshooting; for every number mentioned here, see Limits and costs.

Symptom Go to
A Code thread paused, stopped, or ended Didn't work Code threads
A preview won't start, or a phone link stopped working Previews and phone apps
A cloud thread won't start, or can't reach a website Cloud
A file is refused, or an answer doesn't use your documents Ask and colleagues
A chart or a View doesn't show, or a file doesn't open Views and documents
A notebook has no chapters, or an answer can't be marked Learn
Visitors see that a public colleague is resting or unavailable Public colleagues
A routine is waiting, stopped, or didn't run Routines
Credits ran out, or a low-credit warning appears Credits and billing
Ask can't find a conversation, an issue or a repository Integrations and plugins
You can't sign in, or a link in an email doesn't work Sign-in
Set up with Ysra stops, or a part fails Set up with Ysra

Code threads#

“I paused because the credits ran out. Your changes are saved. Tell me to continue once there are credits.”#

Why: the balance reached zero; a task checks before each paid step and pauses instead of going on.

What to do:

  1. Add credits or wait for the plan's monthly refill (Plans and billing).
  2. Tell Ysra to continue in the same thread. It picks up where it paused.

The thread list can say the same thing as “I stopped at the limit set for this work. Your changes and what I checked are kept; add credits or raise the limit, then tell me to continue.” It is the same pause; the same steps apply, or raise the limit set on the task.

“I paused because this account is paused. Your changes are saved. Write to support@ysra.ai.”#

Why: the account itself is paused; no work can run on it. Nothing is deleted.

What to do:

  1. Write to support@ysra.ai.
  2. Once the account is resumed, tell Ysra to continue. See A paused account.

“I paused because Ysra was closed on this folder.”#

Why: a thread on your computer runs in the desktop app or the CLI; with the app closed on that folder, nothing can run.

What to do:

  1. Open the folder again in the desktop app or the CLI.
  2. The task carries on; its work was kept.

The task ended Didn't work#

Why: the change is made and kept, but the project's checks fail or the app doesn't start. The thread says what failed, and the receipt line says what ran.

What to do:

  1. Read what failed.
  2. Use or deliver the change anyway, ask for a fix, or Continue.

See How a Code thread works.

A check fails that has nothing to do with my change#

Why: it is a pre-existing failure: it was already failing before the thread started. Ysra reports it separately and doesn't count it against the change.

What to do:

  1. Fix it on your default branch, or
  2. Mention it in the goal if you want Ysra to fix it too.

The thread keeps hitting the same failure and stops#

Why: the same check kept failing the same way, or the work stopped making progress. Ysra stops rather than go round in circles.

What to do:

  1. Read the last failure: it usually points to something outside the code, such as a service, test data or a setting the tests expect.
  2. Steer the thread with that information and continue. See Steering and saved points.

Everything passed, but criteria show as unproven#

Why: some requirements describe behaviour that has to be exercised in a browser, and no browser check ran. Ysra reports those as unproven, not passed.

What to do:

  1. Ask for a browser check in a follow-up. See Evidence and verification.

“I used up my automatic recovery attempts.”#

Why: the machine running the task was lost several times, and Ysra stopped picking the task up by itself.

What to do:

  1. Continue: a new task starts from where the last one stopped, with the changes kept.

Ysra asks before installing something#

Why: installs happen only with your OK.

What to do:

  1. Approve it once in the thread. See Install tools with your OK.

Undo changes… undoes nothing: “… I left everything as it is.”#

Why: you edited one of the task's files yourself since; Undo never overwrites your own work, so it changes nothing at all.

What to do:

  1. Put the files back by hand, or go back to an earlier saved point.

Previews and phone apps#

“The preview didn't start in 3 minutes.”#

Why: the app is slow to start, or waits for something it can't reach.

What to do:

  1. Read the last log lines shown under the message.
  2. Choose Ask Ysra to fix it (a paid change), or Start preview again.

“The app stopped. Here are its last lines.”#

Why: the app crashed.

What to do:

  1. Choose Ask Ysra to fix it.

The preview stopped by itself#

Why: 15 minutes with nobody looking, a task needed the machine, or the plan's longest task was reached.

What to do:

  1. Start preview again.

Why: preview links last 12 hours.

What to do:

  1. Open the preview from the thread again.

“Your phone's Expo Go runs SDK N; this app uses SDK M, so Expo Go won't open it. Move the app to SDK N.”#

Why: Expo Go opens only projects made for the SDK it runs, and the phone that scanned decides.

What to do:

  1. Choose Move to SDK N (a paid change). Ysra moves the project, runs Expo's checks, fixes what breaks and restarts the preview.

“… uses the newer SDK M. Update Expo Go from the App Store or Play Store, or move the app to SDK N.”#

Why: the phone's Expo Go is older than the app.

What to do:

  1. Update Expo Go on the phone, then scan again, or
  2. Choose Move to SDK N.

See Phone apps and the Expo SDK.

Why: a phone link works only while the thread's machine runs.

What to do:

  1. Start the preview again from the thread and scan the new QR code.

Cloud#

“Ysra’s cloud comes with a plan. Pick one in Billing, or run this on your own computer.”#

Why: without a plan there is no cloud.

What to do:

  1. Choose a plan in Billing, or
  2. Run the work on your computer with the desktop app or the CLI.

“Your plan runs N cloud tasks at a time.”#

Why: each plan has a number of cloud threads at once (Starter 1, Pro 2, Max 4, Team 2 per seat).

What to do:

  1. Wait: the task starts when one finishes.
  2. Or run it on your own computer.

“Ysra’s cloud is busy right now. Your task starts as soon as a machine frees up.”#

Why: every machine is in use for now.

What to do:

  1. Leave the thread: it starts by itself.
  2. If it still hasn't started, send the message again later.

“That’s a lot of cloud tasks in an hour.”#

Why: each plan has a number of machine starts an hour (Starter 6, Pro 15, Max 30, Team 15).

What to do:

  1. Try again in a few minutes, or run it on your own computer.

“This month’s N cloud hours are used.”#

Why: the plan's cloud hours for the month are spent (Starter 20, Pro 80, Max 250, Team 40 per seat).

What to do:

  1. Wait for the 1st of the month, or
  2. Work on your own computer, which still works, or move to a larger plan.

A command in the cloud can't reach a website#

Why: the cloud machine reaches only your code host and the project's package registries (npm, PyPI, Go, crates, RubyGems, Packagist, Maven).

What to do:

  1. Run that part on your own computer, or
  2. Give the needed files to the thread instead of a download link.

The thread's machine was gone after a day#

Why: a paused machine is deleted 24 hours after its tasks end. The saved files stay.

What to do:

  1. Send the next message: a fresh machine starts with the saved files.

See In Ysra's cloud.

Ask and colleagues#

“That’s a lot of help questions for one day.”#

Why: help questions (the ? in the app) are free, up to 20 a day.

What to do:

  1. Read these docs, or
  2. Send the conversation to the Ysra team with Get help.

“… is in an older Office format. Save it as … and upload that.”#

Why: older Word and PowerPoint files (.doc, .ppt) are refused. Older Excel files (.xls) are accepted.

What to do:

  1. Save the file as .docx or .pptx, then upload it again.

“This kind of file isn’t supported.”#

Why: only some file types can be read. See Files.

What to do:

  1. Save it as PDF, Word (.docx), PowerPoint (.pptx), Excel (.xlsx), CSV, TSV, Markdown, text, HTML, JSON, RTF or an image, then upload that.

“Today’s allowance for reading scanned pages and pictures is used up …”#

Why: scanned pages and pictures are read up to 3,000 a day per person.

What to do:

  1. Upload the file again tomorrow to have the rest read.

An answer doesn't use my documents#

Why: the file may still be being read, couldn't be read, or isn't in the colleague's sources.

What to do:

  1. Check the file's state in the workspace's files.
  2. Check the colleague's sources. See Colleagues and Sources and citations.

Views and documents#

“This interactive visual can't be shown here.”#

Why: the app or the screen you're on can't run the interactive part.

What to do:

  1. Choose Open the View to open it on its own page, or
  2. Ask for a chart or a picture instead.

“This View isn't available. Open it again from your Ysra conversation.”#

Why: the link is incomplete or out of date.

What to do:

  1. Open the conversation the View belongs to, and open the View from there.

“No preview for this file”#

Why: Ysra couldn't draw the first pages of this file.

What to do:

  1. Choose Download and open it in Word, PowerPoint or another app that reads it.

“This file can't be used here: a picture in it goes against Ysra's acceptable use policy.”#

Why: a picture in the file was refused by the upload check. See Acceptable use.

What to do:

  1. Remove the picture and upload the file again.

“We couldn't check this file safely, so it wasn't added.”#

Why: the file is encrypted, or too large to check.

What to do:

  1. Upload a smaller or unencrypted copy of the file.

“Videos can't be uploaded here.”#

Why: Ysra reads documents and still images, not videos.

What to do:

  1. Upload a still image (PNG, JPEG, WebP or GIF) or a document instead.

Learn#

“No chapters found in these files yet.”#

Why: the notebook's files are still being read, or have no text Ysra can read.

What to do:

  1. Wait for the files to finish reading, then open the notebook again.
  2. Check the files in Library → Files, and add course files with readable text.

“Couldn’t mark this answer. Try again.”#

Why: marking didn't finish.

What to do:

  1. Choose Mark my answer again.

“Part of your work couldn’t be read. Try a clearer photo, or type it.”#

Why: some of the photo of your work wasn't legible.

What to do:

  1. Take a clearer, well-lit photo, or type that part of the answer.

Public colleagues#

Visitors read “This assistant is resting for now.”#

Why: a limit was reached (per visitor per hour, per day, or the month's credits), or the owner is out of credits or paused.

What to do:

  1. Check the colleague's limits and raise one if it is too low. See Public link.
  2. Add credits if the balance is empty.

Visitors can still leave a question and an email address meanwhile.

Visitors read “Lots of people are asking right now. Try again in a moment.”#

Why: too many questions arrived at the same moment.

What to do:

  1. Ask again a little later; nothing needs changing.

“This assistant isn’t available.”#

Why: the link is switched off, never existed, or Ysra switched it off for misuse.

What to do:

  1. Check that the colleague is still published.
  2. If Ysra switched it off, write to support@ysra.ai: only support can turn it back on.

“This assistant isn’t available on this website.”#

Why: the website isn't in the colleague's list of websites (up to 10).

What to do:

  1. Add the website to the colleague's list. The link's own page always works.

A file is refused: “… has no text a visitor’s question can search …”#

Why: the file is still being read, couldn't be read, or has nothing written in it.

What to do:

  1. Wait a few seconds after an upload and try again, or choose another file.

Routines#

A run is Waiting for you#

Why: a step will send something (an email, a message) and waits for your approval of the exact text.

What to do:

  1. Open the run, read the text, then Approve or Reject. See Runs and approvals.

“No one approved this within 7 days, so I didn't do it. Run it again when you're ready.”#

Why: an approval waits 7 days, then the step is dropped.

What to do:

  1. Run the routine again and approve the step in time.

“This run reached its … spending limit, so it stopped.”#

Why: a run spends 200 credits at most by default.

What to do:

  1. Raise the run's limit on the routine (up to 5,000 credits), or make the job smaller. See How routines work.

“This routine reached its … limit for today, so it stopped. It runs again tomorrow.”#

Why: a routine spends 1,000 credits a day at most by default (midnight UTC).

What to do:

  1. Wait for the next day, or raise the daily limit (up to 5,000 credits).

The routine doesn't run on its schedule#

Why: Routines start Not started or are Paused; or the schedule is read in the routine's time zone (UTC if none).

What to do:

  1. Check that the routine is On.
  2. Check its time zone. See Schedules.

A routine card says “To draft or send email, connect the mailbox a routine uses: Integrations → Gmail for a routine.”#

Why: the job sends mail, and no mailbox is connected for routines.

What to do:

  1. Connect Gmail for a routine. See Gmail.
  2. Start the routine from the card again.

Credits and billing#

“The credits ran out. Add credits, or wait for the plan's monthly refill.”#

Why: the balance is zero, so new paid work doesn't start.

What to do:

  1. Add a credit pack or change plan in Plans and billing, or wait for the monthly refill.
YOUR WORK YOUR CREDITS Work uses credits threads, routines, Machines, Ask Credits run low a warning at 10% or less left Credits run out Ysra pauses before its next step your changes are saved Credits are added plan refill, a credit pack, or an automatic top-up You say continue the work picks up where it paused 1 2 3 4 5
Running work pauses before its next paid step; nothing done is lost.

“This account is paused. Write to support@ysra.ai.”#

Why: the account is paused by Ysra; no work can run.

What to do:

  1. Write to support@ysra.ai. Nothing is deleted.

A low-credit warning appears#

Why: 10% of the plan's credits or less are left.

What to do:

  1. Add credits, or turn on an automatic top-up.

“Voice needs about N credits to start …”#

Why: voice needs 2 minutes' worth of credits to start.

What to do:

  1. Add credits, or keep typing.

“You've used this month's N voice minutes.”#

Why: each plan has voice minutes a month (no plan 10, Starter 60, Pro 300, Max 1,000, Team 120).

What to do:

  1. Keep typing: it uses no voice minutes. The minutes come back on the date shown.

A Mayz review doesn't start#

Why: a review on its own isn't started below 100 credits.

What to do:

  1. Add credits, then start the review again. See Mayz reviews.

Integrations and plugins#

Ask doesn't find a conversation or an issue#

Why: the app wasn't granted that conversation, the issue is on another site, or the first sync hasn't finished.

What to do:

  1. Check that the card is Ready and shows “Last synchronized …”.
  2. Use Sync now if the content is new.
  3. Check what was granted. See Slack and Jira.

A repository is missing#

Why: the repository isn't granted to the Ysra app on GitHub, or its access was removed there.

What to do:

  1. Grant the repository to the Ysra app on GitHub. See GitHub.
  2. To work on it with Code, open its folder in the desktop app or the CLI.

A plugin's change never happens in Ask#

Why: a tool that sends or changes something never runs during the answer: it becomes a card that waits for Approve.

What to do:

  1. Read the card under the answer and choose Approve. See Actions and approvals.

Code doesn't change anything in a connected service#

Why: Allow changes in Code is off, so Code uses only the tools that read.

What to do:

  1. Turn on Allow changes in Code on the plugin, if you want Code to change things there without asking. See Plugins, connectors and skills.

A connection shows Reconnect#

Why: the sign-in to that service has ended.

What to do:

  1. Choose Reconnect and sign in to the service again.

Sign-in#

“Too many wrong passwords. Try again in N minutes, or reset your password.”#

Why: after several wrong passwords for one email address, sign-in for it pauses for a few minutes.

What to do:

  1. Wait the minutes shown, or
  2. Reset the password with Forgot password?. See Sign in.

Why: a link works once and lasts one hour.

What to do:

  1. Choose Send a new link.

Why: a verification link works once and lasts 24 hours.

What to do:

  1. Choose Send the link again on the banner in the web app.

“Sign-up isn’t open yet.”#

Why: Ysra is in early access, by invitation only.

What to do:

  1. Open the invitation link someone on your team sent, or
  2. Request access.

Set up with Ysra#

“You've set up Ysra a few times today. Try again tomorrow, or set things up by hand.”#

Why: Set up with Ysra can be started 3 times a day per person.

What to do:

  1. Try again tomorrow, or
  2. Make colleagues and routines yourself. See Colleagues and Routines.

“I couldn't open …” (your website)#

Why: the site couldn't be read, or it is on a private network address.

What to do:

  1. Answer the next question in one line about what the company does. The talk carries on.

A part says Waiting for your file or Waiting for Gmail#

Why: the part needs a document or a plugin connection first.

What to do:

  1. Upload the file, or Connect the plugin.

A part failed#

Why: something went wrong creating that part only.

What to do:

  1. Choose Try again on that part. The other parts are not affected.

“Everything was removed. Keep at least one part, or skip.”#

Why: Start needs at least one part.

What to do:

  1. Bring one back with Undo, or choose Skip.

See Set up with Ysra.

Still stuck?#

Write to support@ysra.ai and say which thread, routine or colleague it is. In the desktop app, see Where the record of Ysra's work is.

YsraDocs