Troubleshoot Possible AIQ Performance Issues

Troubleshoot Possible AIQ Performance Issues

ThereUse isthis article when AIQ feels slow, executions queue unexpectedly, reports load slowly, or test nodes are not keeping up with scheduled demand. Start with environment evidence before changing configuration.

Common areas to review

• Host resources: CPU, memory, disk I/O, and available storage on controller, database, and test-node hosts.
• Database health: Result-table growth, slow queries, retention settings, and backup activity.
• Test-node capacity: Number of concurrent executions, browser/device availability, and node connectivity.
• Scenario design: Excessive waits, unnecessary screenshots, large payloads, and missing cleanup steps.
• Network path: Latency or firewall issues between AIQ services, test nodes, databases, and target applications.

Recommended workflow

1. Capture the exact symptom, affected time range, and AIQ components involved.
2. Review logs and resource metrics before restarting services.
3. Run a wellsmall knownknown-good performancescenario issueto withseparate platform issues from scenario-specific issues.
4. Apply one change at a time and record the Roku Remote Tool environment. To avoid running into it you need to often clear the Automation logs in the Roku Remote Tool.
1. result.

Navigate to the Automation logs.

Scroll to the right until you see the Erase Logs button.

Click the trash bin icon to clear the logs.