Skip to content

HTTP 503 error retry mechanism needs to be added in case of failure. #566

Closed

Description

  1. Please check our current Issues to see if someone already reported this https://github.com/Microsoft/vsts-node-api/issues
  2. Take a look at our Instructions for logging issues https://github.com/Microsoft/vsts-node-api/blob/master/CONTRIBUTING.md#instructions-for-logging-issues

Environment

Node version: 18.x
Npm version: 9.8.1
OS and version: 10
azure-devops-node-api version: 12.1.0

Issue Description

HTTP 503 error retry mechanism needs to be added in case of failure.

Expected behaviour

When a 503 error is thrown there must be one retry to check if it is actually a server error. as subsequent payloads are working

Actual behaviour

statusCode: 503,
responseHeaders: {}

Steps to reproduce

  1. Create test run, test result
  2. Update test result using the const testResult = await testApiObject.updateTestResults(testResultDetails, this.projectName, testRunId);

Logs

Azure DevOps Services
support](https://go.microsoft.com/fwlink/?linkid=242573%22%3Esupport) page.

Ref A: 578F632E34D343B09001185201CA97CB Ref B: BL2AA2030108007 Ref C: 2023-09-01T08:47:11Z
at RestClient.<anonymous> (C:\a\1\s\node_modules\typed-rest-client\RestClient.js:202:31)
at Generator.next (<anonymous>)
at fulfilled (C:\a\1\s\node_modules\typed-rest-client\RestClient.js:6:58)
at processTicksAndRejections (node:internal/process/task_queues:95:5) {

statusCode: 503,
responseHeaders: {}
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions