Troubleshoot Iteration Summary Error Messages

Scenario

Last reviewed: September 28, 2026

YouUse arethis tryingarticle towhen download/analyzean aAIQ reportexecution fromshows an iteration-summary error and the Report option and AIQ displays the following message: "An error has occurred while trying to retrieve the test duration. Iteration Summary may not be available or accurate."

Selected Report Option

Message

Solution / Workaround

This situation can happen when the URL of the RDS database server is changed (or even the password), the parameter config=default used to access the reports,team needs to beidentify whether it came from data, playback, or reporting.

What changed within this article

• Changed the article from a config=<db-config-hash-number>vague error-message title into a troubleshooting workflow.
• Added checks for DPL row availability, failed assertions, step-level output, report generation timing, and thenexecution logs.
• Clarified that the reportsiteration aresummary accessible.is

  an investigation

  entry

  Thepoint, <db-config-hash-number> can be obtained by inspectingnot the URLonly openedsource byof failure evidence.

Validation workflow

1. Open the linkfailed “Clickexecution hereand to see reports” seen incompare the playback-controller.htmliteration page when running a scenario. That number does not change unless you change something in the AIQ database URL or DB user creds.

   Process

1. Navigate to the Run Scenario option.

Select the most recent scenario executed and click Show Results.

Click Click Here.

Take the config ID (Copy) displayed in the URL

Navigate back to the Report Option, select the report that is broken, replace the cID displayed in the URLsummary with the onestep obtainedoutput.

Check inwhether the previousfailing step,iteration andmaps pressto <Enter>,a specific DPL row or input value.Review report/output logs before changing the reportscenario will be displayed and ready to be analyzed.logic.

Review note: This now helps triage data-driven iteration failures instead of just naming the error.