Skip to content

Updating report data

Starting with OctoPerf 17.0.0, test results are stored in a new format. This new format is what lets a report identify an action, a Virtual User or a monitoring counter by its name and its position rather than by an internal identifier - which is what makes results comparable across projects and keeps a report readable after you rename an action.

Results recorded before you upgraded to 17.0.0 are still in the previous format. They are not lost, and nothing is deleted: they simply have to be updated once before their report can display values again.

When it happens

The update runs on demand, one test result at a time. Nothing runs in the background, and no upgrade window converts your whole history at once.

You will see it the first time you open a report built on an older result - whether you come from the reports list or from a report link you had bookmarked. Reports built on results recorded after the upgrade are never concerned.

What you see

Opening such a report opens a dialog that explains what is happening. The dialog does not block you, and from there you have three possible outcomes:

  • You leave it open: the dialog waits for the update to finish, then the report opens automatically.
  • You close the dialog: the update carries on. The tasks menu opens to show you the running task, and you can open the report from that task once it is done. The dialog carries the tasks menu icon next to its title, so you know which icon to look for in the top bar afterwards.
  • The update fails: the dialog closes, the tasks menu opens on the failing task, and the report does not open. The task tells you what went wrong, in the server's own words.

An update is permanent: once a result has been updated, opening its report is immediate and the dialog never appears again for it.

Info

A comparison report or a trend report is built on several test results. Each of them is updated separately, so a report that mixes recent and older results only updates the older ones.

How long it takes

The update rewrites the samples of one test result, so the time it takes is proportional to the volume of that result: a short smoke test is nearly instant, a long test with millions of requests takes longer. You can close the dialog and keep working while it runs - the tasks menu keeps you informed.

If the update fails

The task in the tasks menu carries the reason for the failure. If it does not tell you enough to act on, keep the message and contact our support with it, along with the name of the report.

Exporting an older report

An update is required before the data can be read, so anything that reads the report data is affected until it has run:

  • opening the report in the interface triggers the update through the dialog above,
  • exporting the report as PDF needs the result to be updated first - open the report once, let the update finish, then export.

If you drive OctoPerf from the API or an AI agent

The MCP server knows about this state: a tool that would return empty values on a result that is not up to date says so instead, and points at the tool that runs the update. Report listings are annotated with the results that need one.

If you call the REST API yourself, the check-update-read sequence and the endpoints involved are documented in REST API changes: 16.2 to 17.0.