Review Output Logs in AIQ

Recommended guidance

Use Output Logs as the first evidence source when an AIQ execution fails, behaves differently than expected, or stops before completion. Logs should be reviewed together with the scenario, data source, browser or device, Test Node, and time window.

What to look for

• Execution start and stop timestamps.
• Scenario Editor step failures, assertion failures, and wait timeouts.
• Service Suite request, response, authentication, and parsing errors.
• Browser, driver, mobile, or Test Node errors.
• Repository, file, certificate, proxy, or environment access failures.

Useful troubleshooting pattern

1. Filter the log to the failing execution or the narrowest time window available.
2. Identify the first meaningful error, not only the final error shown at the end.
3. Match the failing step to the scenario, data row, service call, or browser action.
4. Check whether the failure is reproducible with the same data and environment.
5. Attach relevant log excerpts when escalating; avoid sharing secrets, tokens, or full credentials.

Common mistakes

• Assuming a UI failure is an AIQ platform issue before checking data and waits.
• Copying entire logs without removing sensitive information.
• Ignoring earlier warnings that explain a later failure.

Last updated: October 5, 2026