Run config & results

These cover how runs are controlled and how results, reports, and uploads behave. Many are expected behavior — graceful stop/cancel, reports only after completion, and format-restricted uploads.

AllMy Test Run Config isn't listed when starting a run

Run configs are scoped to a specific automation type (Web, API, Performance) and project. A config created for one type won't appear when you run a different type — and a combined performance API + Web run needs a Web config and an API config separately. Create the config under the matching type, in the correct project, and it will appear in the run dialog.

PerformanceSaved a config but it’s not in the Performance list

The “created” notification only confirms the config was saved — not that it belongs to the list you’re viewing. Configs are grouped by automation type: only Web automation and API automation configs appear in their Web and API sections, and all other configs are listed under Performance only. If a config you created isn’t here, open the list for the automation type it was created under.

AccessRun config Create/Edit/Delete options are missing

Managing run configs requires more than ReadOnly access. If the Create button and the edit/delete icons aren’t shown, your project role is ReadOnly — ask a project admin for a higher role.

WebNo screenshots in the result

The Screenshot tab shows a step’s screenshot only when one was captured for it. Screenshots are produced by cloud execution according to the run config’s Screenshot Capture mode — local-agent runs don’t capture screenshots, so their results have none. If you expect screenshots, run on the cloud and make sure the run config’s capture mode isn’t restricting them (e.g. failure-only modes only attach screenshots to failed steps).

CloudStop or Cancel doesn't take effect immediately

Stop and Cancel are graceful — the run shows "will be stopped/cancelled soon" and transitions through STOPPING before reaching its final state. Allow a moment for the run to wind down rather than re-issuing the action repeatedly.

PerformanceUpload rejected: "not a valid file type"

Performance uploads accept only JMX or CSV files. Other formats are rejected. Export a valid JMeter .jmx plan or a .csv data file and upload again.