- what it saw, in the recording and screenshots
- what it did, in the actions
- what went over the network, in the requests, traces and logs
- what it concluded, in the result


Header
The breadcrumbs lead back to the project. Next to the title, runs tied to a GitHub, GitLab or Bitbucket repository link to the commit and the pull request or merge request. On the right, a badge shows the result, or the status while the run has no result yet. The strip below the title summarizes the run:- The result, the run’s name, and its type, trigger and attempt, for example Web · Vercel · attempt 1.
- The callbacks that report the result back to Vercel, GitHub, GitLab, Bitbucket or Netlify.
- Run details, the info icon, which opens the run’s facts: its name and id, project, trigger, type, attempts, duration, credits, why it ended, when it was created, started and ended, any error, and the delivery of each callback.
- The duration, the credits, and how many actions, requests and screenshots the run recorded.
≤ and the most it can use while it runs. When the run wasn’t charged, Run details adds the reason after the number, such as “not charged: the run never started”.
A run refused because the team’s credits for the month were used up shows Refused in Run details, with the date the credits reset, instead of an error. See When credits run out.
Watch a run live
While a run on IronBee is in progress, the page shows it live: the browser view, every action as it executes, and the network requests behind it. The stage goes through Authorizing, Connecting to the run and Waiting for the first frame before the stream starts. The live view is for watching. Owners, admins and members can open it, and the stage shows how many people are watching. Billing admins can’t watch a run live. When the run ends, the page switches to the recording as soon as it’s uploaded. See The recording.

The recording
After a run, the recording replays what the run saw:- Play, and scrub with a preview on hover.
- Change the speed: the smart speed moves quickly through idle stretches.
- Go fullscreen.
- Keep the actions, the network and the logs synced to the playback position.


Actions and screenshots
The left panel lists what the run did:- Actions is every step, in order. Filter the list, or turn on Only IronBee tools to hide everything else. Hover a step and click Show details to see the tool call and its result. Copy raw event copies it.
- Screenshots shows every screenshot the run took.
The result
The result panel shows the verdict of the run:
When the verdict lists findings, the tabs are Summary, Checks and Findings, and a link to Issues or Suggested fixes opens Findings. The count on Findings takes the color of the worst finding’s severity. Otherwise, as on a passing run, an older run or a CLI verification cycle, the tabs are Summary, Checks, Issues and Suggested fixes.
You can resize the panel, collapse it, or swap it with the recording.
Findings
Findings lists what the run found, worst first. Each row shows:- The severity: Critical, High, Medium or Low.
- The category: Correctness, Security, or Docs, names and tests, the same categories as code review.
- The file and line, such as
src/cart.ts:42. - The title: what goes wrong.
- Happens when, Then, Seen and Impact: what triggers the problem, what happens next, what the run saw, and what it costs.
- The diff: for a run tied to a pull request, the part of the pull request’s diff that holds the finding’s line, with the lines the run quoted marked.
- Suggested fix, open by default: a note on what to change, and the code to put in. When the code replaces lines around the finding, the heading says which, such as replaces lines 12–14, and if the pull request’s diff holds those lines, the code shows as a diff against them. Otherwise the code shows on its own under the file’s path, or under The code to put in when the finding names no file.
- Where this rests: other places in the code the finding relies on, each linked to the file at the verified commit.
← and → to move, and Esc to close.
Network, traces and logs
The right panel inspects what went over the wire:- Network lists every request the run made.
- Open a request to see its General, Request, Response and Others details.
- Bodies show as Preview or Raw.
- Traces shows the run’s spans as a tree, with a bar for each span’s timing. Search the spans, and open a span to see its details. The footer counts the spans and the errors among them.
- Logs lists the log records the run collected.
Keyboard shortcuts
Share a view
The page’s URL keeps the selected tab, panel, step and screenshot, and the finding open in the dialog. Copy it to point a teammate at the exact moment you are looking at.What’s next?
Verifications
Every run of a project, with its trigger, status and result.
Scenarios
Flows written in plain words, run against an environment one action at a time.