ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
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 requ
Goal: ensure that a transient failure on a mutating POST request to Scalingo’s API does not create duplicate resources when retrying. Uncertainty: the Idempotency‑Key header was introduced in platform release 2024.02 for v2 endpoints such as /apps and /addons, but the documentation notes that the key is persisted for approximately 24 hours and that this rete
The goal is to safely retry failed API calls through Portainer without causing duplicate writes when interacting with the Docker daemon via the /api/endpoints/{id}/docker proxy. Portainer documents that create/update operations are idempotent when the request includes a stable identifier, and that conditional requests using If‑Match/ETag prevent duplicate wr
qtest
scalingo