Skip to main content
Use this when you need to know what happened in one call, for example because a customer asks about a price, or how often an application ran in the last days.

​
Before you start

  • You hold evidence:read and usage:read in the environment, for example as an auditor (Who may do what).
  • You know the correlation ID the caller sent in X-Correlation-Id, or the run ID from the answer’s X-Run-Id header (Call a release over REST).

​
Find a run

1

Open Runs

Open the Admin UI (the cluster address followed by /runtime-management/ui/), click Sign in with Leapter and sign in with your Leapter account. Choose the environment in the environment list at the bottom of the sidebar, and click Runs. In a narrow window, the sidebar is hidden: open it with Toggle Sidebar, the button at the top left. The page lists the runs this cluster recorded for the environment, the newest first. Test runs in the Lab are not listed.
2

Search for the correlation ID

Type the correlation ID in the search field, here order-1042, and press Enter. The list shows every run whose correlation ID contains what you typed, in upper or lower case, so longer IDs that contain it are listed too. A * in the search stands for any characters. Check the Correlation ID column; in a narrow window, scroll the table to the right to see it. If the caller sent the same correlation ID more than once, each of those runs is listed, the newest first: tell them apart by the time in Started. The Admin UI shows times in your browser’s time zone.
The Admin UI Runs page for playground. The search field contains order-1042 and has a green ring. One run is listed: Success, Oct 21, 2026, 3:16:09 PM, 8 ms, application pizza-pricing-calculator-180269, the blueprint's ID, release v1, correlation ID order-1042.

The Runs page, filtered to one correlation ID.

The Blueprint column shows the blueprint’s ID. To narrow the list without a correlation ID, use the buttons Success, Error, Timeout and Limited, or Filters.
3

Open the run

In the row of your run, click its status, here Success. The run’s page opens. It shows the facts of the run, the Payloads with the Input and the Output, and Replay, which shows the blueprint with the values of this run.
The page of run 0d5e32b5-373a-4b2b-b740-dc3ca7cff9aa. Status success, Started Oct 21, 2026, 3:16:09 PM, Duration 8 ms, Application pizza-pricing-calculator-180269, Blueprint ID, Run kind Released, Release version v1, Content digest, Correlation ID order-1042, Initiated by curl. Below, the Payloads card shows the input with toppings bacon, crustType stuffed, dayOfWeek tuesday, pizzaSize medium, and the start of the output.

The page of one run: its facts and its payloads.

The run ID at the top is the X-Run-Id the caller got. The search field takes correlation IDs only. To open a run by its run ID, open the Admin UI’s address followed by runs/?env=<environment>&id=<run-id>, for example https://cluster.example.com/runtime-management/ui/runs/?env=playground&id=0d5e32b5-373a-4b2b-b740-dc3ca7cff9aa. Opening an address signs you out of the Admin UI: click Sign in with Leapter again, and the run’s page opens.

​
Read usage

1

Open Usage

Click Usage in the sidebar. The page counts the runs of the environment chosen in the sidebar, by default for the Last 7 days. The tiles show Runs in window, Runs per day, Busiest day and Applications.
2

Choose an application

Click Filters, choose the application under Application, and close the filter with Esc. The page now shows Per blueprint: runs, runs without error, errors, timeouts, the error-free rate and how long the runs took. By step shows the blueprint with the share of runs that reached each step, and how many runs were traced, for example “39 of 51 runs traced”.
The Admin UI Usage page with Last 7 days and Filters (1). Tiles: Runs in window 51, Runs per day over 7 days 7, Busiest day 51 runs 2026-10-21, Applications filtered to pizza-pricing-calculator-180269 1. Below, a bar chart of runs per day, the table Runs per application, and the start of the table Per blueprint.

Usage for one application over the last 7 days.

The counters at the top count every run the cluster recorded, also runs whose data was deleted since. The Per blueprint table counts only the runs the cluster still keeps, so its totals can be lower.

​
Result

You found the call by its correlation ID and read what went in and what came out, and you know how much the application ran.

​
Troubleshooting

After Sign in with Leapter, you are in the Lab and not in the Admin UI. Open the Admin UI’s address again and click Sign in with Leapter once more. The Status page opens.

​
What to do next