> ## Documentation Index > Fetch the complete documentation index at: https://docs.newly.app/llms.txt > Use this file to discover all available pages before exploring further. # Messages explained > What the messages you see in Newly v2 mean, what to do next, and whether your work is safe. This page lists messages you may see in Newly v2, at app.newly.app and in Newly for Mac. Each row says what the message means and what to do. If yours isn't here, or the suggested fix doesn't work, see [Getting help](/help/getting-help). Start with [Is my work safe?](#is-my-work-safe) if something went wrong in the middle of a change. ## Credits | Message | What it means | What to do | | ---------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- | | "You’re out of credits, so this run stopped here. Everything so far is saved." with **Buy more credits →** | Your organization ran out of credits during a turn. The agent stopped. Work finished before that point is kept. | Add credits, then send another message in the same chat. See [Running out of credits](/billing/out-of-credits). | | "Pick a plan to start building with Newly." | Your organization has no plan or credits yet, so the agent can't start. | Choose a plan in **Billing**. See [Plans and top-ups](/billing/plans-and-top-ups). | | "Your organization needs a plan" | You're a member of an organization that has no plan yet. Only owners and admins can pick one. | Ask an owner or admin of your organization to start a plan. | | "Ask an admin or owner of your organization to add credit." | You're a member, and your organization's balance is empty. | Ask an owner or admin to add credits. | | "One-time credits can be added once you have a plan." | Your account needs a plan before it can buy one-time credits. | Start a plan first. See [Plans and top-ups](/billing/plans-and-top-ups). | | An error that mentions 402 | You're out of credits, or you've hit a usage limit. | Add credits, or wait and try again later. If it keeps happening, contact support. | | "This environment's shared daily AI budget has been reached…" | A Newly-wide daily limit was reached. It isn't about your balance or your account. | Try again later. The limit resets at midnight UTC. Contact support if it persists. | ## Chats and sessions A session is the environment a chat runs in. Some messages use that word. | Message | What it means | What to do | | -------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- | | "You’ve reached the active session limit. Your prompt is saved as a draft." with **Free a slot** and **Retry** | Your organization already has as many Remote chats starting or running as it can by default. Parked and Local chats don't count. See [Parked chats and limits](/build/sleep-and-limits#how-many-chats-can-run-at-once). | Press **Free a slot** to find a running chat you can stop, or wait and press **Retry**. Your prompt is kept. | | "You already have as many sessions running as your plan allows. Finish one you are done with, then try again." | Your new chat waited for a free slot, and none opened in time. The limit is a default for every organization, not tied to what your plan costs. | Stop or finish a chat you no longer need, then send your message again. See [Parked chats and limits](/build/sleep-and-limits). | | "Parked — your next message resumes it" | The chat was idle and went to sleep. See [Parked chats and limits](/build/sleep-and-limits). Your code is saved. | Send a message to continue. | | "This turn reached its one-hour limit. Your saved work is safe; send another message to continue." | By default, a single turn can run for up to one hour. | Send another message. Ask the agent to continue where it left off. | | "The agent stopped unexpectedly. Your last saved work is safe; send another message to continue." | The agent's run ended before it finished. | Send another message. If the agent seems to have forgotten the conversation, briefly restate what you were doing. | | "\[The model finished this turn without producing a visible reply.]" | The agent ended its turn without writing a reply, even after retrying. | Send your message again, or rephrase it. | | "Earlier messages summarized to free up space — your full history stays here" | The conversation got long, so the agent summarized older messages to keep working. You can still scroll through everything. | Nothing. If an early detail matters, mention it again. | | "View only" with "You can read this project and watch what the agent does. Ask its owner for edit access to send prompts." | You have **Can view** access to this project. | Ask the project owner for **Can edit** access. See [Share a project](/code/sharing-projects). | | "Read-only" with "This chat runs in the desktop app. Open Newly on your computer to continue the conversation." | This is a Local chat from Newly for Mac. You can read it on the web, but not send messages. | Open the Mac app on that Mac to continue, or start a new chat. | | "Couldn't start your cloud session" | The chat couldn't start. The card explains why. | Follow the card's advice and try again. If it keeps happening, press **Copy debug info** and contact support. | | "Your cloud session stopped" | A running chat stopped. The card explains why. | Follow the card's advice. Depending on the cause, send another message or start a new chat. | | "Couldn't reopen your cloud session" | Newly couldn't safely resume the chat, so it stopped instead of risking your files. | Start a new chat in the same project. Your saved code is still in the project. | | "The connection to your session dropped. Send another message to pick up where you left off." | The connection to the chat was lost. | Send another message. | | "Your app changed somewhere else while you were working here. Combine the changes?" with **Yes** and **Not now** | Another chat in this project changed the code since this chat last worked on it. | Press **Yes** to combine the changes. Press **Not now** to hold off. | | "Sync paused" | Two chats changed the same part of the app, and the agent can't safely combine them. | Tell the agent which change should win, or ask it to merge them by hand. | In Local chats (Mac), the failure card titles say "local" instead of "cloud". ## Undo and restore | Message | What it means | What to do | | ----------------------------------------------------------------- | ------------------------------------------ | ---------------------------------------------- | | "Restored that version. Your next message will continue from it." | The restore worked. | Send your next message. | | "The agent is still working. Stop it before restoring a version." | You can't restore while a turn is running. | Press **Stop**, then restore. | | "There's no earlier version to undo yet." | There's nothing earlier to go back to. | Nothing to do. | | "Couldn't restore that version." | The restore didn't complete. | Try again. If it fails again, contact support. | See [Undo and Restore to here](/code/undo-and-restore). ## Attachments | Message | What it means | What to do | | -------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------- | | "*name* is not a supported image. Use PNG, JPG, WebP, or GIF." | The image is in a format the agent can't read, such as HEIC. | Convert it to PNG or JPG and attach it again. | | "Could not upload the attached file. Try pasting it again." | The upload failed. A common cause is a file or chat over the size limits. See [Size limits](/build/attachments-and-voice#size-limits). | Check the file size, make it smaller if needed, and attach it again. | See [Screenshots, files and voice](/build/attachments-and-voice). ## Preview | Message | What it means | What to do | | ------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------- | | "The agent changed native code. Update to install the new build." with **Update** | Your simulator is running an older build. | Press **Update**. | | "Couldn't build your app" with **Build again** | The native build failed. The agent usually starts a turn to fix it on its own, unless you pressed **Stop**. That turn uses credits like any other. | Wait for the agent, or press **Build again**. | | "Couldn't start your simulator" with **Try again** | The simulator didn't start. | Press **Try again**. | | "Your simulator went idle" with **Resume** | Your simulator was released after a period without use, or because the chat parked. | Press **Resume** to start a fresh device with the newest build. | | "Waiting for an available Android build worker. Your build will start automatically." | Your Android build is in a queue. | Wait. If it waits too long, it fails with advice on retrying. | | "App preview failed" | The Web view couldn't start. | Press **Retry starting preview**. The first load can take a few minutes. | | "Session is sleeping" | The Web view's address was opened while the chat was parked. | Send a message, or press **Restart server** in the Web view to wake the chat. | See [Previewing your app](/preview/overview) and [Using the cloud simulators](/preview/simulators). ## Publishing to TestFlight | Message | What it means | What to do | | ------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | "An organization owner or admin must connect Apple and authorize the upload." | Only organization owners and admins can connect Apple and publish. | Ask an owner or admin to publish. | | "Publishing requires a saved Newly cloud project." | This chat's project isn't saved as a Newly cloud project, so it can't be published from here. | Publish from a Remote chat in a Newly cloud project. | | "Could not prepare the app source for publishing. Retry after checking the project source." | Newly couldn't package your project for the build. | Ask the agent to make sure the project uses a plain `app.json` (no `app.config` file) and has no very large files, then press **Retry**. See [Ship your iOS app to TestFlight](/publish/testflight). | | "Apple did not return a developer team for signing…" | The Apple account has no active Apple Developer Program membership, or no access to Certificates, Identifiers & Profiles. | Check the membership and access in your Apple account, then press **Retry team lookup**. | | "Too many signing certificates" | Your Apple team has reached its limit for distribution certificates. | Press **Manage signing certificates**. See [Connect Apple and manage signing](/publish/connect-apple). | | "Signing certificate needs attention" | There's a problem with a signing certificate. | Press **Manage signing certificates**. See [Connect Apple and manage signing](/publish/connect-apple). | ## Backend and AI in your app These messages come from your app's backend. You may see them in your app, or the agent may report them. | Message | What it means | What to do | | ------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | | "Your Newly credits are too low for this request." | Your app asked an AI model for something, and your organization's balance can't cover it. | Add credits. See [AI features in your app](/backend/ai-models). | | "The App AI request limit has been reached. Try again later." | One of your app's users reached their daily request limit, or too many requests were already running in this project environment. See [Limits](/backend/ai-models#limits). | Try again later. | | "App AI is temporarily at capacity." | A Newly-wide limit was reached. It isn't about your balance. | Try again later. | | "Enable this model for the project first." | Your app called a model that isn't turned on for this environment. | Ask the agent to enable the model. | | "Managed Newly agent sessions can operate only on the dev backend" | The agent tried to change your production backend. It can only work on dev. | Deploy to production yourself with the newly CLI. See [Production and secrets](/backend/production-and-secrets). | | "You do not have any credits left." | Creating a Newly Backend needs a positive balance. | Add credits, then try again. | ## Is my work safe? Usually, yes. Here's how to check and what to do. 1. **Check the latest saved version.** Newly saves your code at the end of every turn that changed files. Look for the most recent **Restore to here** under your messages, and check the preview. 2. **Restate what you were doing.** After a failure, the agent may not remember the earlier conversation, even though your code is there. Send a short summary of what you were working on and what's left. 3. **Go back if needed.** If the latest change broke something, use **Restore to here** on an earlier message. See [Undo and Restore to here](/code/undo-and-restore). 4. **Contact support with details.** On a failure card, press **Copy debug info** and paste the result into your support message. It contains identifiers only, never passwords or tokens. See [Getting help](/help/getting-help). If you think a failed chat used credits it shouldn't have, contact support with the project and chat.