Banners you may see
Studio shows a strip across the top of the screen when something outside your own work needs attention. Read this when one appears; the two notices that belong to a single conversation are on the board and mentions and files, previews and approvals.
The banners
| Banner | What it looks like | Your run | What to do |
|---|---|---|---|
| Amazon Bedrock throttling | Amber (red for the daily quota); names the run; ends with a Quota docs link and an X to dismiss. A fixed strip on every screen for a workflow run (click it to open the run); above the thread for a chat run. | See below. | Wait, then re-send or re-run; tell your administrator if it repeats. |
| Amazon Bedrock is unavailable | Amber; one sentence naming the model, its role and the AWS Region, a details line, an AWS Health link and an X to dismiss. The same words appear inside the chat turn or workflow step that failed. A fixed strip on every screen. | The call to that model failed; other models carry on. | Wait; see below. |
| Model not enabled in Amazon Bedrock | Red; one sentence naming the model, its role and the Region, a details line, a Bedrock model access link and an X to dismiss. The same words appear inside the chat turn or workflow step that failed. | Every call to that model fails until it is enabled. | An administrator enables the model; see below. |
| AlphaAgent Studio was updated | "AlphaAgent Studio was updated. Refreshing to load the latest version…" with Refresh now. Studio checks every 60 seconds and when you return to the tab, then reloads 4 seconds later. | Continues on the server; reopen it after the refresh. | Nothing, or Refresh now. Unsent composer text is not kept. |
| Billing alert | "Billing alert:" plus a message from your AlphaAgent Console account, such as "A payment on your account is overdue.", "Your AlphaAgent runtime is frozen pending payment of an overdue invoice." or "A billing issue requires attention."; a "Freezes in" pill and a Pay invoice link may show. Cannot be dismissed. | Unaffected. | Administrators: Pay invoice or the Console (licences, usage and billing); anyone else tells the administrator before the freeze date. |
| MCP connector alerts | One strip per connector and reason, amber or red, with the connector's name and Open connector; dismiss hides it for this session. | Agents that use that connector may be unable to. | See below. |
| Service halted (licence) | Red, "Service halted" plus the reason. The deployment refuses every request with HTTP 451: Send is disabled, workflows cannot start, lists fail to load, Profile shows Licence Blocked. Re-checked every 20 seconds; clears when the check passes. Cannot be dismissed. | You cannot follow, steer or stop it until the block lifts; written files stay. | Contact your administrator; the messages are below. |
| Your session has expired | Full screen: your sign-in session timed out, and Studio can no longer act for you until you sign in again; "your work is safe"; one button, Sign in again. | Unaffected. | Sign in again. If the notice returns, your company login is refusing you; ask your administrator to check your assignment. |
| Signed out | The page after Sign out: You are signed out, with Sign in again. Sign-out can instead end on a Microsoft page; you are signed out all the same. | Unaffected. | Sign in again when you want to come back, or open the Studio address. If Sign in again ends on "Authorization Required", open the Studio address again. |
The Amazon Bedrock throttle banner: three states
Amazon Bedrock runs the models behind your agents and limits the tokens each AWS account may send per second and per day. Every message ends "please contact AWS to raise your Bedrock quotas."
| State | The message | What happened | Clears |
|---|---|---|---|
| Slowed (amber) | "Amazon Bedrock is rate-limiting", with the run, the measured tokens per second, the window and the threshold, then "AlphaAgent is now adjusting its output speed and will re-evaluate in … seconds". | Nothing was paused or re-sent; output arrived slower than expected and the run continues at Bedrock's pace. | By itself after the seconds named, unless the next measurement trips it again. |
| Refused (amber) | "Amazon Bedrock returned a ThrottlingException for" the run, with Bedrock's own error. | The AWS client had already retried, so that request failed: in chat the step reads Failed; in a workflow the node fails with "Agent execution failed". Other steps carry on. | By itself; then re-send or re-run the failed step. |
| Daily quota exhausted (red, "Service halted") | "Amazon Bedrock has exhausted today's per-account token quota for model", then "All AlphaAgent operations using this model are halted until Bedrock's daily window resets." | Every call to that model from any user fails until AWS resets the window; shown to everyone signed in. | Not by itself; the event is kept for up to 24 hours. Dismissing hides it in your browser only. |
Quotas belong to the AWS account the deployment runs in; your administrator raises them with AWS through Quota docs. This is one reason each deployment has its own account (Before you start).
Amazon Bedrock is unavailable, or a model is not enabled
When Amazon Bedrock cannot serve a model, Studio says so everywhere you wait on it: the banner, and the same words in the chat or workflow step that failed. The banner clears by itself when the model answers again.
| Headline | The message | What to do |
|---|---|---|
| Amazon Bedrock is unavailable | "Amazon Bedrock is temporarily unable to serve" the model, "the" role (Coordinator model, Worker model or Chat-title model) and "in" the Region. "This is a problem on the Amazon Bedrock side; AlphaAgent will work again when Bedrock recovers. If it continues, your AWS administrator can raise it with AWS Support using the details below." | Nothing is wrong in AlphaAgent. If it continues, your AWS administrator raises it with AWS Support using the details line; the AWS Health link shows AWS's own status. |
| Model not enabled in Amazon Bedrock | The model and its role "is not enabled for this AWS account in" the Region. "An administrator enables it in the Amazon Bedrock console." | An administrator enables the model in the Amazon Bedrock console (Bedrock model access opens AWS's instructions), then re-send or re-run. |
Under the message, one selectable details line gives what AWS Support asks for: Bedrock error (the error code and HTTP status), Model, Region, Request ID (AWS's own, left out when the call carried none) and Time in UTC (or First failure and Latest failure when they differ). Copy details on the banner copies the line.
MCP connector banners
A banner names the connector and opens its page with Open connector. Errors show before warnings. Studio checks every active MCP connector about every 15 minutes, so a banner appears or clears within that time of the change, or at once when a call hits it.
| Banner | Colour | Who sees it | What to do |
|---|---|---|---|
| "connector is not responding. Agents cannot use its tools until it recovers." | Red | The connector's owner (everyone on a governed deployment) | Check the server and its address on the connector's page; it clears when the server answers again. |
| "connector: the credential expires in n days." ("in 1 day" for one) | Amber | The connector's owner (everyone on a governed deployment) | Add a new credential before the date shown in Expires on. It starts 7 days before. A credential managed by your organisation is replaced by your administrators. |
| "connector: the credential has expired. Add a new one to keep using it." | Red | The connector's owner (everyone on a governed deployment) | Add credential on the connector's page. |
| "connector: connect your account again to keep using it." | Amber | The person whose sign-in expired or whose connector settings changed | Open the connector and press Connect again (Each person signs in to an MCP connector). It clears when you are connected. |
| "connector: connect your account so your runs can use it." | Amber | The person whose run needed a connection and had no one to ask | Connect your account on the connector's page. |
| "connector is blocked by your organisation's policy." | Red | The connector's owner, or the person whose call was refused | Ask your administrator to allow its server and sign-in method, or change the connector (Connector policy, credentials and activity). It clears once an evaluation allows it. |
Service halted messages
| Message | Meaning |
|---|---|
| "AlphaAgent cannot reach the AlphaAgent Console and has been disabled." | The licence check could not complete; clears on the next successful check. |
| "AlphaAgent has been disabled by your administrator." | The licence is not valid, no specific reason. |
| "This license is not active." | The key was set inactive in the Console. |
| "This license has been revoked." | Halted until your administrator re-activates the deployment. |
| "AlphaAgent has been suspended due to an unresolved billing issue." / "by your administrator." / "pending review of an acceptable-use issue." / "as a security precaution." | A billing, manual, acceptable-use or security hold. |
| "Your AlphaAgent trial has ended." | The trial licence expired. |
| "This AlphaAgent deployment has been decommissioned." | The deployment was retired. |
| "AlphaAgent is temporarily unavailable for scheduled maintenance." | A maintenance hold; try again later. |
| "AlphaAgent Studio is unavailable: the AlphaAgent Console license phone-home check has failed." | The licence check itself is not running. |
Each message ends by asking you to contact your administrator; their side is in Console: licences, usage and billing.
Notes
- The Bedrock strip shows one warning at a time, the newest; a daily-quota event always wins. Studio never shows how much quota is used and has no setting to raise it; the banner is the only signal.
- Service halted stays after your administrator says the licence is fine: wait a minute, then reload; if it persists the deployment still cannot reach the Console. The update banner shows but does not reload: Refresh now.