Receiving Notifications (Early Access)

This feature is in the Early Access stage and under active development. Configuration schemas and behavior are subject to change. We recommend that you do not use this feature in production environments.

Solace Agent Mesh notifies you when something you started finishes or needs your attention, for example when a scheduled task completes or an agent waits for your approval. This page covers viewing and answering notifications in the Agent Mesh UI, choosing which notifications reach you, and receiving them as direct messages in Slack or Microsoft Teams. For more information about setting up the notification service, see Configuring Notifications (Early Access).

Understanding Notifications

Notifications appear in your in-app inbox in the Agent Mesh UI. Agent Mesh also sends them as direct messages in Slack or Microsoft Teams after you enable that application. On this page, a channel is a place where notifications reach you: your in-app inbox, Slack, Microsoft Teams, or a destination that your administrator configured for you.

Each notification has a notification type, which the inbox shows in its Category column. Every notification type in the following table is on by default, and you can turn off the ones you do not want.

Notification type Group When Agent Mesh sends it
Scheduled task results Agents and Tasks A scheduled task that you own or created completes, fails, or times out. The notification carries the agent's reply, or the error when the run failed. For more information, see Getting Notified About Runs.
Messages from agents and workflows Agents and Tasks An agent or workflow sends you a message with the notify_user tool, for example to report a result.
Tool approvals and agent input requests Requests and Sharing An agent waits for you to approve a tool call or to answer a question. For more information, see Answering an Input Request.
Chats shared with me Requests and Sharing Another user shares a chat with you.
Budget alerts Budget A budget that applies to you crosses its alert threshold or reaches its limit. If you administer budgets, you also receive alerts about the Agent Mesh and system-user budgets. For more information, see Managing Model Spend with Budgets.

The Budget group appears only when your deployment uses budgets. Settings lists the budget alerts as separate notification types, so you can turn each one off on its own:

  • For every user: Approaching my budget threshold and My budget reached.

  • If you administer budgets: Approaching Agent Mesh budget threshold, Agent Mesh budget reached, Approaching a system user budget threshold, and System user budget reached.

Notifications that an administrator or another application sends through the notification REST API, and some reports that Agent Mesh generates automatically, have no notification type. They always reach your inbox, and you cannot turn them off.

Viewing Notifications

The Notifications item in the navigation bar shows how many unread notifications you have, or 99+ when you have more than 99. The count updates as soon as a notification arrives, and again when you open the panel or return to the browser tab.

To view your notifications:

  1. In the navigation bar, click Notifications. A panel opens with your 12 most recent notifications, grouped under Today, This week, and Older. An unread notification has a blue bar and a bold title.

  2. Click a notification. The Notifications page opens with that notification expanded.

  3. If the notification refers to a chat, click View Chat to open it. An approval or input request that still waits for your answer shows Respond in Chat instead; for more information, see Answering an Input Request. What opens depends on the notification:

    • A chat shared with you with Viewer access opens in the shared-chat view, and a chat shared with Editor access opens as a chat.

    • A completed scheduled task run links back to its chat for the task's owner.

    • An expired or answered request opens its chat with View Chat.

    • Failed runs have no View Chat link.

To see every notification, click See all in the panel. The Notifications page lists your notifications in a table with Title, Category, and Time columns, 25 to a page, newest first. Times are in your browser's time zone.

You can narrow and read the notifications on the Notifications page in these ways:

  • To list only notifications that you have not read, turn on Show only unread notifications.

  • To list one notification type, select it in the category drop-down list. To list every type again, select All categories.

  • To read a notification's full text, click the expander arrow at the start of its row. Agent Mesh marks the notification read when you expand it, except for an input request that still waits for your answer.

To manage a single notification, click the Notification actions icon (three dots) at the end of its row and select one of these items:

  • Mark as read or Mark as unread changes the notification's read state.

  • The Turn off item names the row's notification type, for example Turn off "Scheduled task results" notifications. It stops that notification type for every channel, including your inbox. Rows for approvals and input requests do not offer this item, because those notifications always reach your inbox.

  • Delete removes the notification permanently.

To mark every unread notification read, click Mark all as read at the bottom of the panel that opens when you click Notifications in the navigation bar, or at the top of the Notifications page. On the Notifications page, when you select a notification type in the category drop-down list, the button marks only that notification type read.

Answering an Input Request

When an agent asks you a question or asks you to approve a tool call, the notification shows a Needs response soon badge. You answer the request in the chat it came from, where you can see the conversation that led to it. Agent Mesh accepts the first answer it receives, wherever you give it.

To answer an input request:

  1. On the Notifications page, find the row with the Needs response soon badge.

  2. (Optional) To see what the agent asks, the chat to answer it in, and when the request expires, click the expander arrow at the start of the row.

  3. Click Respond in Chat on the row. The chat opens with the request at the end of the chat.

  4. Answer the request in the chat. The chat confirms that Agent Mesh received your response, and the agent continues.

When you open a chat that has a request waiting for your answer, the chat shows the request at the end of the chat, whether you open it from Respond in Chat, the list of recent chats, another browser tab, or another device. A request that belongs to no chat shows its form in the row instead, and you answer it there.

A request that expired or that you answered elsewhere shows an Expired badge and no form. Marking an input request read does not answer it, and the Needs response soon badge stays until you respond.

If a request expires before you respond, the agent continues without your answer, and a tool call that waits for approval does not run. A workflow step that waits for your approval fails when the request expires.

Tool approvals also reach Slack and Microsoft Teams after you enable the application, and you can answer them in the direct message. A question that an agent asks during a chat you started in the Agent Mesh UI goes only to your inbox.

Choosing Which Notifications You Receive

You choose, for each channel, which notification types reach you. The Notifications section of Settings holds these choices.

To change your notification settings:

  1. Open the Notifications section of Settings. To do so, click Settings in the Notifications panel, or click Notification Settings at the top of the Notifications page.

  2. Select the channel to change from the tabs at the top. The tabs appear only when you can receive notifications on a channel besides In-App. A tab appears for each channel that you can receive on, such as Slack, Microsoft Teams, or a destination that your administrator configured for you. The In-App tab controls your inbox. Each tab shows how many notification types are on for that channel.

  3. Turn each notification type's toggle on or off. Agent Mesh saves each change immediately.

You cannot turn off the In-App toggle for Tool approvals and agent input requests, because an agent that waits for your answer can get it only if the request reaches you. You can turn the type off for Slack or Microsoft Teams.

Receiving Notifications in Slack or Microsoft Teams

Agent Mesh can send your notifications as direct messages from the Agent Mesh application in Slack or Microsoft Teams. It never posts them in a Slack or Microsoft Teams channel. The External Application Notifications part of the Notifications section of Settings lists the applications that your administrator has connected.

How Agent Mesh finds you depends on the application:

  • In Slack, Agent Mesh looks up the Slack account whose email matches the email that you log in to Agent Mesh with. You do not need to message the application first.

  • In Microsoft Teams, Agent Mesh identifies your account from a message that you send to the Agent Mesh application, and then sends notifications to a private one-to-one chat with you. Send the application a message before you click Enable.

To receive notifications in Slack or Microsoft Teams:

  1. Open the Notifications section of Settings.

  2. Under External Application Notifications, click Enable on the Slack or Teams card.

  3. Wait for the card to show Enabled. The page shows a banner that confirms the application is enabled, and the application may send you a short confirmation message.

  4. (Optional) To limit what the application sends you, select its tab at the top of the Notifications section and turn off the notification types that you do not want it to receive.

After you enable an application, every notification type starts on for it, whatever you chose on the In-App tab. A type that you turned off with a row's Turn off item stays off everywhere.

To stop receiving notifications in an application, click the Slack actions or Teams actions icon (three dots) on its card and select Disable. Agent Mesh keeps your per-type choices for that application, so they apply again if you enable it later.

Notification Retention

Agent Mesh deletes a read notification after a retention period that your administrator sets, 30 days by default, counted from when Agent Mesh sent the notification. Agent Mesh never deletes unread notifications automatically. To remove a notification sooner, delete it from its row's Notification actions menu.

Troubleshooting

Use the following entries when notifications do not appear or you cannot enable Slack or Microsoft Teams.

The Navigation Bar Has No Notifications Item

The navigation bar has no Notifications item, and Settings has no Notifications section. The notification service is turned off for your deployment, or the deployment that serves the Agent Mesh UI does not run it.

Ask your administrator whether notifications are turned on for your deployment. For more information about the operator steps, see Enabling and Disabling Notifications.

Enabling Slack Fails with an Account Lookup Error

Clicking Enable on the Slack card shows an error that Agent Mesh could not find a Slack account for your login email. The email on your Slack profile differs from the email that you log in to Agent Mesh with.

To resolve this issue:

  1. In Slack, open your profile and check its email address.

  2. Change your Slack profile email to the address that you log in to Agent Mesh with, or ask your administrator to align the two.

  3. Click Enable on the Slack card again.

Enabling Microsoft Teams Fails Before You Message the Application

Clicking Enable on the Teams card shows an error that Agent Mesh has not received a message from this user in Microsoft Teams. Agent Mesh identifies your Microsoft Teams account only from a message that you send to the application.

To resolve this issue:

  1. In Microsoft Teams, open a chat with the Agent Mesh application and send it any message.

  2. In the Notifications section of Settings, click Enable on the Teams card again.

Notifications Do Not Arrive in Slack or Microsoft Teams

The application's card shows Enabled, but notifications appear only in your inbox.

To resolve this issue:

  1. Select the application's tab in the Notifications section of Settings and check that the notification type is turned on for it.

  2. Check that the Agent Mesh application can send you direct messages in Slack or Microsoft Teams, for example that it is installed and that you have not blocked it.

  3. Ask your administrator whether the Slack Entrypoint or Teams Entrypoint is running. On a Solace event broker, notifications sent while it is stopped arrive after it starts again.

What Next?

You can now follow and answer notifications from the Agent Mesh UI, Slack, or Microsoft Teams. For more information about the notifications that scheduled tasks send, see Scheduling Tasks (Experimental).