Automatic retry for Test Execution Engine failures when context missing

Recommended action: abort, do not automatically retry

For the error "Test run failed: Unable to locate test execution context," the Test Execution Engine should abort the deployment rather than automatically retry the run. A missing execution context is typically a data or mapping problem—such as an invalid test run ID, missing project or module mapping, or integration version mismatch—not a transient failure. Retrying without recreating the missing context will likely repeat the same failure and can delay detection of a configuration error.

Confirmed facts versus uncertainty

Item	Status
Automatic retry recommended for missing context	No; abort is the safer default
Configuration setting that toggles retry for this exact error	Not verified in available qTest documentation
Documented behavior across supported qTest versions	Unverified; check official release notes for your deployed version
Root cause identifiable from the log string alone	No; the log does not name the configuration file or run ID source

Steps for this case

1. Treat the failure as fatal and abort the deployment until the missing context is resolved.
2. Inspect qTest administration and integration configuration files referenced by the deployment logs for any error-handling or retry section related to test execution. Do not add or change retry keys without official documentation.
3. Search official qTest documentation for the exact error string and your deployed version to confirm whether a retry setting exists.
4. Review the deployment job configuration and qTest server logs to determine whether the referenced test run ID exists in the qTest database.

Safe read-only verification commands

grep -R "Unable to locate test execution context" /path/to/qtest/logs/
grep -R "retry" /path/to/qtest/integration-config 2>/dev/null || true

Replace /path/to/qtest/ with the actual installation directory. These commands only search files and do not modify configuration.

Missing diagnostic detail

Confirm whether the missing context is caused by an invalid test run ID, a missing project or module mapping, or an integration or plugin version mismatch. This detail determines whether a retry could ever succeed or whether the deployment configuration itself must be corrected first.

Assumption: this guidance applies to qTest deployments where the Test Execution Engine controls run scheduling. Version-specific behavior is not confirmed, so treat this as a draft for human review against official qTest documentation for your version.