Two runs can look identical in a list and be completely different jobs. The thing that tells them apart is usually a value buried in the payload. Now you can pull that value out and give it its own column.
Smart columns
A smart column reads a single value straight out of a run and shows it for every row. Point one at the run's payload, metadata, or output with a JSON path, give it a label, and pick how it renders: $.order.total as a number, $.customerId as text, $.status as a badge. It lands alongside the built-in columns and fills in down the whole list.
Smart columns are display-only, so they never touch the sort or filter that keep the list fast. A run whose payload doesn't carry the path shows a placeholder instead of a value, and values too large to inline are marked rather than fetched row by row. The list keeps polling, so smart-column values fill in as new runs arrive.
Show, hide, and reorder
The Columns control sits on every runs list. Show the columns you care about, hide the ones you don't, and drag them into the order you actually read. ID, Task, and Status stay pinned so a run is always identifiable; everything else, from Duration and Machine to Queue, Region, and Tags, is yours to arrange. The same control drives every list built on the runs table: the global list, and every per-task, scheduled, agent, and webhook view.
Views you can share
Your column layout lives in the page URL, so a view is just a link. Set up the columns for a particular investigation, bookmark it, and drop it in a thread for a teammate who opens the exact same table. Pair it with Favorites and a tuned runs view sits one click away in your sidebar.
Try it
Open Runs, hit the Columns control, and add your first smart column. It's live in your dashboard now.