Every failure the assistant reports is one sentence naming the actual cause, followed by at most one control. You will never see a raw error code, a stack trace, an internal identifier, or a bare "something went wrong" where the real reason was known.

Each sentence also tells you the one thing you most need: whether anything was changed. A sentence that says nothing was changed means exactly that.

• "Too many requests right now. Wait a moment and try again." You sent messages faster than the limit allows. Nothing was lost. Send it again in a few seconds.
• "You have several conversations running at once. Wait for one to finish." You have hit your own limit on simultaneous runs. Let one finish, or stop one you no longer need.
• "Your team is using a lot of AI right now. Try again in a moment." Your whole organization is at its simultaneous limit. It clears as your colleagues' work finishes.
• "Rate limited: try again in 12s." Under the message box, with the Send button counting down. It sends normally once the count reaches zero.

• "Your seat can't make changes with the assistant. Ask an admin for a Power seat." You can read and ask questions, but changing records through the assistant needs a Power seat. A read-only seat sees a matching sentence saying nothing was changed.
• "Laureo isn't set up for this workspace yet. Ask an admin to turn it on in Settings." The assistant has not been enabled for your organization.
• "Your trial has ended. Upgrade your plan to keep using Laureo."
• "Not enough AI credits left this month for this action. Ask an admin to add Extra AI Credits." The monthly AI credits are one pool for the whole organization and reset on your billing cycle. The same line appears when some AI credits are left but fewer than the action needs. An admin can add Extra AI Credits or upgrade the plan in Settings > Company > Billing. See AI Setup.
• "You've used all of your personal Laureo AI time this month. Ask your admin to raise your limit." Your own AI credit cap for this month is used up, even though the organization may have more AI credits.
• "Paused: payment hold" A payment failed and your workspace is on a payment hold, so the assistant is off until billing is updated. An admin can fix it in Settings > Company > Billing. See Payment holds.
• "AI features are paused until billing is updated. An admin can update it in Settings > Company > Billing." The workspace's plan or billing needs attention: a trial or a subscription that ended, a subscription you paused, or a payment problem. An admin can fix it in Settings > Company > Billing.

A single action can also be refused on its own, without stopping the conversation. See Approval settings for the ones your organization controls, and the next section for the one line Laureo shows.

When Laureo cannot do an action from the chat, it says so once and does not try again another way. This is not a failure: nothing was changed, and the step shows an arrow rather than a cross.

• "This is done on the Tasks page." With an Open Tasks button under it, naming whichever page the action belongs to. The page opens only when you press the button, and the conversation stays with you in the dock.
• "This is done in the app, not in the chat." The same, for an action with no page you can open from here.
• "Your role does not include this.", "Your seat does not include this." or "Your plan does not include this." In general words, with no button and no page name.
• "That page cannot be opened from here." You asked for a page this conversation cannot open for you.

• "You stopped this response." You pressed Stop. This is a state of its own, not a failure, and it is reported quietly. Anything the run had already done stays, honestly recorded.
• "This did not finish. Some steps had already run." Something failed partway. The steps listed above it landed and nothing after them did.
• "This response ran longer than one turn allows, so it stopped. Ask for a smaller piece of it in a new chat." Offered with a New chat control. Break the request into parts.
• "The assistant could not be reached, so this response did not finish." A transient outage. Try again.
• "The assistant lost track of this task. Try again." The work stopped being reachable and was closed rather than left spinning forever.
• "Laureo did not answer. Nothing was changed." The answer came back empty. Send it again.
• "Your permissions changed during this conversation. Please try again." Your role or access changed mid-run, so the run stopped rather than continuing under authority you no longer had.

• "Still working. This is taking longer than usual." A slow run, not a stuck one. Offered with Stop.
• "No progress from the assistant. You can stop and try again." Nothing has moved for a while. Offered with Stop and Retry.

Both notices withdraw themselves the moment the run starts moving again, so a slow patch does not leave a warning sitting over work that recovered.

• "You are offline. Messages will fail until your connection is back." A line above the message box. Work already accepted carries on without you.
• "Live updates paused. Refresh to see new messages." The live view lost its connection after repeated attempts. Reloading replays the saved events in order. Nothing is lost.
• "The connection dropped before the answer finished. Nothing was changed."
• "Your session ended. Sign in again to continue this conversation." Offered with a Sign in control. Your conversation is still there when you come back.
• "Already running. Showing live progress." You sent into a conversation that was already working. Rather than starting a second run, Laureo attaches you to the one in flight.

• "This approval is no longer active." The run moved on or the proposal was already settled, so your decision would have applied to something else. Nothing was changed. The line adds "Start a new request to continue." and offers a New chat control.
• "Edited actions must be previewed again before approval." You changed a field on the card and approved it without previewing the change. Nothing was changed, and a Review a Fresh Preview control is offered.
• "This card changed. Review the new one." You saved changes from Edit while the card was being replaced. Nothing was changed: read the newer card and decide on that one.
• "A required field is not set. Select Edit or Request changes to fill it in." Under a card whose Approve is off because a field the page's own form requires is empty. Select Edit to type the value, or Request changes to say what it should be. A linked record, such as a company, is not typed in the form: say it in Request changes. When a value on the card is also cut short, the card first asks you to select Show all, and Edit comes on once you have read every value. A card with several changes reads "A required field is not set. Deny this and say what to fill in."
• "This proposal expired before it was approved. Ask again if you still want it." A proposal nobody answered for 48 hours closes its run rather than holding the conversation open forever. Send the request again to pick it back up.
• "This conversation was deleted or is no longer available." Offered with a New chat control.
• "Could not send that decision. Open the task to try again." From the approvals chip, when an approve or deny could not be delivered. It never claims a decision landed when it did not.
• "Could not load your conversations." With a Retry control, in the conversation list.

When Send is unavailable, the reason is written under the box rather than left for you to guess:

• "Message too long: trim to 5,000 characters."
• "Remove unavailable context before sending." One of your attachments could not be prepared.
• "Checking your file. Up to 70 seconds left, then you can send. Remove it to send without it." A file you attached is still being read. The line names the file and counts down the most it can take; if the check does not finish in that time it stops, says so, and lets you send without the file.
• "your-file.pdf could not be checked, so it will not be sent with your message." The safety check on a file stopped without finishing. Your message can still go, and the file is left out of it; you can attach it again.
• "Attached context exceeds the 40,000 token limit. Remove one or more items." Too much attached material for one message.

Attachments themselves are refused before they are stored, never accepted and then quietly ignored:

• "This file is over the 25 MB upload limit." and "This file is empty."
• "Files up to 3.5 MB can be checked for safety right now, and this one is larger." Every file is checked for safety before the assistant reads it, and larger files cannot be checked yet. You are told when you pick the file, before anything is uploaded.
• "This file did not pass the security scan. Remove it to continue."
• "Images are not supported yet. Attach a text, Office, or PDF file instead." when reading images is switched off for your organization.
• "Reading images is on the Business plan and above. Upgrade to attach images, or attach a text, Office, or PDF file instead." when your plan does not carry it.
• "This context is no longer available. Remove it and add it again." when the file or record moved or your access to it changed after you attached it.

A refusal about a file stays as a line under the message box with a Dismiss control, rather than as a notice that disappears before you have read it. It clears when you dismiss it, when you send, or when you attach something else. It deliberately does not clear just because you carried on typing.