API Testing: Run History

Updated

API Testing: Run History

Overview

Use this page to review, filter, and delete API flow test run results. A flow is a saved sequence of API requests that LoadGen executes as a test; every execution, whether started manually, on a schedule, or from elsewhere, produces a run with a pass/fail outcome, a duration, and a start time. Run History is where you check those outcomes and spot failures.

Flows are built and run from the API Testing module, and scheduled executions set up in API Testing: Schedules land here automatically alongside manual runs. This page only displays what those executions produced; it does not create or edit flows. Run records are not kept forever: the retention period shown on this page, adjustable in Configuration: API Testing: Retention, controls how long they remain before LoadGen removes them.

On this page you can narrow the list to a specific flow, run state, or date range, read each run's Pass and Fail counts and duration, and delete runs you no longer need, one at a time or in bulk.

Key concepts

  • flow - A saved sequence of API requests that LoadGen executes as a test. (related: API Testing: Flows)
  • run - A single execution of a flow, recorded with a start time, a duration, and a pass/fail outcome. (related: API Testing: Schedules)
  • retention - The number of days LoadGen keeps a flow's run history before deleting it automatically. (related: Configuration: API Testing: Retention)
  • state - The outcome of a run, such as Completed (passed) or Failed, shown as a colored pill in the State column.

When to use it

  • After a flow runs, manually or on a schedule, to confirm it passed or see why it failed.
  • To review one flow's reliability history over time by filtering on it specifically.
  • To list every Failed run across all flows at once by filtering on State.
  • To check runs from a specific day or incident window using the From and To date filters.
  • To delete runs you no longer need before the retention period removes them automatically.
  • To check the current retention setting and see how far back your run history goes.

Before you begin

  • At least one flow exists and has run at least once; flows are created on API Testing: Flows.
  • Your role can list flows if you need to use the Flow filter; otherwise it is not shown and you see all runs you have access to.
  • Your role can manage retention if you need to change how long runs are kept, which is done on Configuration: API Testing: Retention.

Common workflows

Check whether a specific flow's latest run passed

Persona: load-test operator

  1. Open the Flow dropdown and select the flow you want to review.
    • Expect: The dropdown now shows the selected flow name instead of All Flows.
  2. Select Search.
    • Expect: The table reloads showing only runs for that flow, most recent first.

Verify: Only rows matching the chosen flow appear, and you can read each run's State, Pass, and Fail counts to confirm whether the latest execution succeeded.

Find every failed run across all flows

Persona: load-test operator

  1. Open the State dropdown and select Failed.
    • Expect: The dropdown shows Failed selected instead of All.
  2. Select Search.
    • Expect: The table reloads showing only runs whose State is Failed, across every flow.
  3. Read the Fail column for each row to see how many checks failed.
    • Expect: No table change; you confirm the Fail counts behind each red State pill.

Verify: Every visible row shows a red Failed pill; if a row shows Failed with a Fail count of 0, the run ended in an execution error rather than a failed check.

Delete a run you no longer need

Persona: operator with run-delete permission

  1. Select the trash icon under Actions for the run you want to remove.
    • Expect: A confirmation prompt appears asking whether to delete the run for that flow and start time, noting this cannot be undone.
  2. Confirm the deletion.
    • Expect: The run disappears from the table.

Verify: The deleted run is no longer listed in Run History; reapplying the same filters no longer returns it.

Steps

Step 1

Open Run History from the API Testing section.

Expected result: The page loads with the run list for every flow you can access, the Flow, State, and date filters set to their defaults (All Flows, All, no dates), and the most recent runs listed first.

Run History is where you review flow executions and their pass/fail outcomes before deciding what to filter or delete.

  • The retention line shows Retention: 180 days and no count limit, with a Change link to the retention settings.
  • Each row lists Flow, State, Started, Duration, Pass, Fail, and an Actions delete icon. API Testing: Run History - step 1

Field reference

Field Purpose Format / Validation Required Default
Flow Limits the run list to one flow instead of every flow you have access to. Leave it on All Flows to scan across your whole API Testing history, or pick a specific flow when you only care about that test's track record. dropdown, list of flow names No All Flows
State Limits the run list to one outcome. Choose Failed to quickly see every run that needs attention, or Completed (passed) to confirm a run or period was healthy; leave All to see every outcome together. dropdown No All
From Limits the list to runs that started on or after this date; combine with To to bound a review window such as the days around an incident. The date matches the run's start day as shown in the Started column, and LoadGen converts it to UTC when you select Search. date, dd/mm/yyyy No -
To Limits the list to runs that started on or before this date; combine with From to bound a review window. date, dd/mm/yyyy No -
Select all runs Selects every run currently loaded on the page in one action so you can delete them together instead of one at a time. checkbox No unchecked
Select run Marks an individual run for inclusion in a bulk delete, without affecting the other rows. checkbox No unchecked

Column reference

Column What it shows How to read it
Flow Identifies which flow produced this run. Select the flow name to open that flow.
State Shows the outcome of the run. A red Failed pill means the run had at least one failing check or an execution error; Completed (passed) means every check in the run succeeded.
Started Shows when the run began. Times are shown in your account's configured time zone; use this column with the From/To filters to locate a specific run.
Duration Shows how long the run took to execute from start to finish. A duration noticeably longer than the flow's usual runs can point to slow API responses or network latency during that run.
Pass Counts how many checks within the run succeeded. Shown in green; compare to Fail to see the proportion of the run that succeeded.
Fail Counts how many checks within the run failed. Shown in red; a nonzero Fail count explains why the run's State is Failed even if other checks passed.
Actions Provides the delete control for this specific run. Select the trash icon to delete just this run.

Controls reference

Runs the query using the current Flow, State, From, and To values and reloads the table.

When to use: After changing any filter field, to apply it to the run list.

Side effects: Read-only: reloads the run list, does not change any data.

Clear filters

Resets Flow, State, From, and To back to their defaults (All Flows, All, empty dates) and reloads the full run list.

When to use: When you want to return to the unfiltered run history after narrowing it down.

Side effects: Read-only: clears filter values and reloads data, does not delete any runs.

Clear

Resets a single filter field in the bar without affecting the others.

When to use: When only one filter, such as a date, needs to be removed while keeping the rest of your search.

Side effects: Read-only: clears one field's value and does not change the others.

Delete selected runs

Permanently deletes every currently selected run after you confirm the prompt.

When to use: When you have selected multiple runs you no longer need.

Side effects: Mutating: deletes the selected run records; LoadGen asks you to confirm because this cannot be undone.

Delete run

Permanently deletes this single run after you confirm a prompt naming its flow and start time.

When to use: When one specific run is no longer useful to keep.

Side effects: Mutating: deletes the run record; cannot be undone.

Previous

Loads the previous page of runs.

When to use: When there are more runs than fit on one page and you want to move back a page.

Side effects: Read-only: changes which runs are displayed.

Next

Loads the next page of runs.

When to use: When you want to see older runs beyond the current page.

Side effects: Read-only: changes which runs are displayed.

Back to Flows

Navigates back to the Flows page.

When to use: When you are done reviewing run history and want to edit or run a flow.

Side effects: Read-only navigation; no data changes.

Change

Opens the retention settings for API Testing runs.

When to use: When you need to extend or shorten how long run history is kept.

Side effects: Read-only navigation from this page; the retention value itself is changed on the destination page.

Go to Flows

Navigates to the Flows page when no runs exist yet.

When to use: When Run History shows no runs at all and you need to create or run a flow first.

Side effects: Read-only navigation.

Verify the result

The run list for your flows is populated with rows showing Flow, State, Started, Duration, Pass, and Fail; selecting Search after setting a filter narrows that list without errors. If the page instead shows 'No Runs', no flow has executed yet; if it shows 'No runs match these filters', loosen or clear the Flow, State, or date filters. A permission message in place of the table means your role cannot read API Testing runs, which is different from there being no history to show.

Troubleshooting

  • Symptom: The Flow dropdown doesn't appear in the filter bar. Fix: Your role can read runs but not list flows; use the State and date filters instead, or ask an admin for a role that can list flows.
  • Symptom: The table shows 'No runs match these filters' even though you expect results. Fix: Select Clear filters to confirm runs exist at all, then reapply Flow, State, or date filters one at a time to find which one is excluding them.
  • Symptom: The table shows 'No Runs' instead of any history. Fix: No flow has run yet; select Go to Flows, run a flow, then return to Run History.
  • Symptom: Runs you expect from a given date are missing after filtering by From/To. Fix: The date filter matches the run's start day as shown in the Started column and is converted to UTC when you select Search; widen the range by a day on each side for runs near a day boundary.
  • Symptom: A permission message appears instead of the run list. Fix: This means your role cannot read API Testing runs, not that there are no runs; ask an admin to grant the needed role.
  • Symptom: The Change link next to the retention line is missing. Fix: Only roles permitted to manage retention see this link; ask an admin to update it on Configuration: API Testing: Retention or request that permission.
Was this article helpful?
0 out of 0 found this helpful