Communication monitor
See separately whether the center accepted a message and whether it actually appeared in the recipient's conversation. Use it when a sent message gets no response.
When to use it
Check how far a message traveled. Center acceptance and actual arrival in the agent's conversation are different events, so the monitor separates them. Open Communication monitor from the sidebar's system row.
assets/turtlecenter/ui-communication-monitor-1.png · Recommended size: 1600×900Two top tabs—Communication flow and ngrok monitor—with the table and detail panel. Prefer a view containing both green and yellow rows.Acceptance versus arrival
Acceptance means the center received and queued the message. Arrival means the center confirmed the message appeared as user input in the recipient's conversation. Acceptance alone does not mean the recipient has read it. Messages move through these steps.
| Stage | Meaning | Display |
|---|---|---|
| 1. Accepted | The center received and queued the message. | Center accepted · Arrival unconfirmed |
| 2. Sent | The center sent it to the recipient room's input. | SENT To be confirmed |
| 3. Arrived | Confirmed that it appeared as actual input in the recipient's conversation. | Final arrival confirmed (green) |
| Failure | A failure during delivery was confirmed. | Failed (red) |
Communication flow tab
A recent-message table with a detail panel below. It queries on opening and refreshes every five minutes while visible. This tab has no Refresh button. It shows the newest 20 messages from the current center run, newest first. Restarting the center starts an empty list.
With no messages, the detail panel says No message flow observed in the current process generation. The center may have just started or no message has been sent yet.
Table columns
| Column | Meaning |
|---|---|
| Time | Time of the last recorded event for the message |
| Sender | Sender name; Unknown if unavailable, Unregistered for an unregistered endpoint |
| Recipient | Recipient name, using the same rules as Sender |
| Center processing | How far the center processed the message |
| First failure | Code for the first failure point, or — if none |
| Queue number | Message sequence number. Include it when asking for support. |
| Final arrival | Arrival confirmed or unconfirmed |
Click a heading to sort; drag it to reorder columns.
Reading colors
| Center processing / Final arrival | Color | Meaning | Action |
|---|---|---|---|
| Final arrival confirmed / Confirmed | Green | The message appeared in the recipient conversation. | None. Agent roomto follow progress. |
| Center accepted · Arrival unconfirmed / Unconfirmed | Yellow | The center accepted it, but arrival is not known yet. | Wait briefly and reopen. If it stays yellow, check the recipient indicator and the Control viewagent status. |
| Failed / Unconfirmed | Red / Yellow | Delivery failed. | Save the First failure code and check the recipient's state. |
Detail panel
Select a row to see its queue number, packet ID, sender → recipient, center processing, and final arrival together. A First failure code is appended when relevant. The first row is selected automatically on opening. Copying these details into a support request helps investigation.
assets/turtlecenter/ui-communication-monitor-2.png · Recommended size: 1600×900A selected row's queue number, packet ID, and outcome in the lower panel.ngrok monitor tab
Shows usage and individual requests arriving at the center from outside. Appears only on centers configured with ngrok external access. To be confirmed Exact conditions for hiding the tab need checking against the deployed UI. It refreshes every five minutes while open.
| Area | Contents |
|---|---|
| Title | Usage statistics · Request monitor |
| Period | Start and end date/time, initially the last day. If start is later than end, it says Start time must be earlier than end time. |
| Refresh / Open Inspector | Refresh queries the selected period. Open Inspector opens ngrok's own request inspector in a browser. |
| Status row | Normal (green), Partial data (yellow), Query unavailable, or No capture. Below are cumulative requests, tunnel starts in the selected period, MCP calls (success/failure), and average/maximum response time. |
| Per-agent table | Agent · Calls · Success · Failure · Average ms |
| Request table | Newest 50 requests: Time · Method · Path · Status · ms |
| Request details | Select a request to see request headers/body and response headers/body on the right. Long content is marked [Partial display]. |
Request details show exchanged headers and bodies as they are. Review them before sharing screenshots. Configure external connections in Settingsunder External connections.
Workflow: a message has no reply
- Open the flow table and find the matching time and recipient. No matching row means the center did not accept that message.
- Green means arrival was confirmed. If there is no answer, check Agent roomfor progress.
- Yellow means accepted but unconfirmed. Wait and recheck; if it persists, inspect the recipient indicator.
- Red means failure. Save the First failure code and queue number. Check the recipient in Control viewagent status.
Things to know
- This monitor is read-only. There are no Resend or Cancel buttons. You decide whether to resend.
- Its list covers the current center run and starts empty after restart.
- The Center processing column may display raw values such as SENT or UNKNOWN. To be confirmed These labels are planned for refinement.
- Arrival unconfirmed means not yet verified, not necessarily failed.