Messages

The Messages view gives you a live feed of everything the runtime is broadcasting over the Messages stream. Use it to watch job progress, confirm workers are healthy, or capture warnings the moment they are emitted. You can pause the feed, filter it, or export the captured data for later analysis.

The panel on the left lists the available channels. Toggle a channel to begin streaming its messages:

Job Status – deployment and lifecycle updates for every job (Deployed, Shutting down, Failed, etc.).
Worker Status – heartbeats and state transitions for connected workers.
Job Messages – application logs that a job emits. Enter one or more job names to subscribe; each job appears as its own channel so you can follow multiple pipelines at once.
Errors & Warnings – the same warnings surfaced in Logs & Issues, delivered as soon as the runtime emits them.
Job Execution Tracking – per-run execution milestones (queued, running, completed) for detailed diagnostics.
Debug: All Messages – a firehose feed intended for short-term debugging. Enable it only when you need full visibility, because it can grow noisy in busy environments.

Active channels stay selected until you disable them. The page remembers your choices for the current browser tab, so you can reload the view without losing subscriptions. This state is not shared across new tabs/windows. If you prefer to start with a clean slate, click Dismiss on the restore prompt or use Clear to wipe the buffer.

Filter and search

Use the Filter by channel checkboxes to focus on a subset of streams while keeping others running in the background.
The search box matches channel names, message types, and the text within each payload. Searches apply instantly and leave the underlying subscriptions untouched.
The counters above the message list show how many messages are currently buffered and the per-minute rate so you can spot bursts at a glance.

Inspect message details

Click any message to open the detail drawer. The UI formats common payloads so you can read them quickly:

Job and worker status messages are summarised with badges for worker, job, and state transitions.
Errors & warnings are grouped into dedicated lists with badges for the affected job or worker and a direct View Logs shortcut.
Job messages show the structured fields that the job emitted; open Raw JSON to copy the original payload.

Every badge in the drawer links back into the rest of the UI. Use Job to jump to the job definition, Worker to open the worker detail page, or View Logs to pivot into the Logs viewer with the worker or job filters pre-filled.

Debugging Triggers and synchronous workflows

Use Debug: All Messages for a short, bounded inspection of Trigger dispatch or a synchronous-response workflow.

Enable Debug: All Messages for a short window.
Search for the invocation_id (from the Trigger invocation record).
Look for the dispatch user-generated message whose payload includes job_event.type: "trigger_invoke".
Confirm that the intended message-triggered job accepted the matching tag.
For a typed synchronous-response workflow, correlate the transport request, workflow run, and terminal response-complete output using the identifiers exposed by that capability.

If you see trigger_invoke but the target does not run, confirm its deployment, worker serviceability, message type, and tag. A new Trigger invocation is dispatch-only; it does not wait for a workflow response. See Triggers for that boundary.

Pause, export, and restore

Hit Pause to stop collecting new entries while you investigate the current buffer. Resume when you want to catch up.
Clear wipes the buffer immediately and resets the persisted state. Choose Export JSON to download everything currently in the buffer.
The viewer keeps the most recent 500 messages in browser storage. When you reload or return to the page in the same tab, you can restore previous subscriptions and continue from where you left off.

Deep links and pivots

Share links to specific channels using query parameters:

?job=<name> subscribes to that job’s messages.
?worker=<id> enables the worker status channel.

You can combine both parameters to prime the page for a particular investigation. The buttons in each message detail also use these parameters when they open the Logs view, so you always land on the relevant subset.

Troubleshooting

If you do not see new messages, confirm the channel toggle is enabled and the Pause button is not active.
Large exports or the Debug feed can fill the buffer quickly. Clear the buffer or turn off unused channels to keep the stream readable.
For end-to-end context on how warnings flow into Logs & Issues, see Logs & Issues.