Search across runs
Find a run by what it produced — search the text of every successful run's result across the workspace.
Sometimes you know what happened but not which run it happened in: a customer quotes an invoice number, a teammate forwards a confirmation id, a webhook response mentions an order. Search answers that question directly. It matches the text of run results — the final output of each successful run — across every run in the workspace, and takes you to the run that produced it.
When to use this
Reach for search when the run id is what you are missing. If you already have the run id or you are working through one run's timeline, open the run instead — the run detail page shows the full step sequence with per-step logs, gates, and retries.
Search from anywhere in Monitoring
The search box sits in the Monitoring header, above Activity, Runs, and Approvals. Click Search runs, or press ⌘K (Ctrl+K on Windows and Linux) from any Monitoring page.
Type at least two characters
Results start after two characters and refresh as you type. Queries are capped at 200 characters — a phrase works better than a paragraph.
Read the grouped results
Matches are grouped by run, newest and most relevant first. Each run shows a snippet of its result with the matched words highlighted.
Open the run
Click a result — or highlight it with the arrow keys and press Enter — to open that run's detail page, with the full step timeline below.
What search can and cannot see
Search reads the same redacted record the run detail page shows you. Values your workspace's redaction rules mask are masked before they are ever indexed, so search can never surface something the run page would hide. It is scoped to the workspace you are in: it never returns a run from another workspace or another account.
Search covers what a run produced, not what happened along the way. It indexes the final result of each successful run — not step-by-step inputs and outputs, and not runs that failed. To find failed runs, filter the run list by status; to inspect a specific step, open the run and read its timeline.
Search covers text, not structure. It matches words in a run's result, so invoice 4021 finds a run whose final output carried that invoice number. It cannot answer "which runs failed on Tuesday" — that is what the run list filters and the Activity feed are for.
When a matched run has aged out
Runs expire on your plan's retention window (see Data handling). A search hit whose run has already expired still shows you the snippet — that text is the answer you were looking for — but it has no link, and the run id is marked as expired. Copy what you need from the snippet; there is no page left to open.
Search returns nothing
No matches at all. Search matches whole words, not fragments: 4021 will not match INV-4021-B as a substring. Try the full token as it appears in the result. Widen to a distinctive word from the message rather than an id you are guessing at.
The run failed. Only successful runs' results are indexed — a failed run never appears in search, whatever passed through it. Filter the run list by status to find it.
The run finished before search coverage began. Runs are indexed from the moment they complete; runs that completed before search became available in your workspace are not indexed retroactively.
The run is older than your retention window. Expired runs leave the index with everything else. Confirm the timeframe against your plan's window in Data handling.
"Search timed out." A very broad query over a busy workspace can exceed the time budget. Add a second word to narrow it and run the search again from the same box.
Related
- Read one run in detail: the per-step timeline, with logs, gates, and retries disclosed at each step.
- Find and filter workflow runs: narrow by status, run id, or workflow when you are not searching by content.
- Debug a failed run: read the error code and provider status on the step that broke.