Stale Execution Record After qTest Agent Termination – Test Runner

Goal: Clarify the retry mechanism used by the qTest Agent when reporting test execution results fails due to network interruptions or API token expiration.

Constraints: The agent must handle asynchronous result reporting, avoid duplicate entries, and maintain consistency with the dashboard; however, the documentation does not specify whether failed HTTP requests trigger exponential backoff, a fixed‑interval retry, or are dropped after a single timeout.

Questions: Does the qTest Agent apply exponential backoff on HTTP 401 or 500 responses? What is the maximum number of retry attempts before the agent stops reporting? Is there a configurable timeout or backoff factor that can be adjusted?