qTest API sync works locally but fails in production

Problem Context

Automated test results are pushed to the qTest server using the Execution API from a CI/CD pipeline. In a local dev environment the push succeeds, but the same configuration fails when the pipeline runs against the production qTest instance.

Constrained Factors

Possible causes include differing project or cycle IDs, API token validity, network restrictions, or API rate limits that are only triggered under higher load. The local runner uses a sandbox project, whereas the production runner targets the live project, and the environment variables are sourced from different secret stores.

Unresolved Questions

Which specific API endpoint or header configuration is causing the authentication or rate‑limit error on production?
Does the production network environment block outbound HTTPS traffic to the qTest API endpoint?
Can we enable verbose logging on the qTest Automation Framework to capture the exact error response during production pushes?