If you see errors when you submit a job and need to raise a support ticket, then please open a ticket by emailing

Please provide the Request-Id and X-Azure-Ref headers, and (if you have it) the Job ID. A response for a successful job should look like this:

HTTP/1.1 201 Created
Content-Length: 20
Content-Type: application/json
Request-Id: df6ec500191bf2c02ee42d519fbea34f
Strict-Transport-Security: max-age=15724800; includeSubDomains
Date: Thu, 23 May 2019 08:59:08 GMT


In this example, the Request-Id is df6ec500191bf2c02ee42d519fbea34f and the Job ID is z2jfp1jwu1.

An error will be reported as a 4XX or 5XX status code; instead of the job ID an error message will be returned. The Request-Id can be included in the ticket to support to help support engineers troubleshoot the problem. Here's an example:

HTTP/1.1 401 Unauthorized
Content-Length: 179
Content-Type: text/html
Request-Id: 00adae505fa8cb7c7f24c6bf52c60048
Strict-Transport-Security: max-age=15724800; includeSubDomains
Date: Thu, 23 May 2019 09:04:49 GMT

<head><title>401 Authorization Required</title></head>
<center><h1>401 Authorization Required</h1></center>

Rate Limited Requests

A 429 error means that the request has been rate limited by our API. This situation could be avoided by adding 1 second delay between requests of the same type, e.g., adding 1 second delay between GET /v2/jobs/{job_id} requests.

results matching ""

    No results matching ""