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."
• "Your team has used this month's included AI budget. An admin can turn on Extra AI Credits or upgrade the plan in Settings > Company > Billing." The monthly budget is a pool for the whole organization and resets on your billing cycle. See AI Setup.
• "You've used all of your personal Laureo AI time this month. Ask your admin to raise your limit." Your own share of the budget is spent, even though the organization may have more.
• "There's a billing issue with your account. Ask your admin to restore AI access."

A single action can also be refused on its own, without stopping the conversation. The refusal names the kind of gate that stopped it: your role does not include it, your seat cannot make changes, the action is above your team's automatic limit, it is switched off for everyone right now, or it needs extra verification only a person can complete. See Approval settings for the ones your organization controls.

• "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 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.
• "Wait for context checks to finish before sending." A file is still being scanned.
• "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."
• "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.