Some requests to /jobs endpoint previously failed with HTTP 422 error
Incident Report for Zamzar
Our operations team have observed that a small number of HTTP POST requests to submit files for conversion to the /v1/jobs API endpoint resulted in an "HTTP 422 Unprocessable" error between March 7th 2018, 14:59:00 UTC and March 8th 2018, 11:53:59 UTC. Additionally the following unexpected response message may have been received by some clients during that time:

{"errors":[{"context":{"parameter":"source_file","reason":"binary data was not successfully received"},"code":11,"message":"an invalid value was specified for a parameter"}]}

This problem which is now resolved was caused by an internal configuration issue within the Zamzar API. The root cause of that problem has been identified and a fix has been put in place to ensure this issue does not reoccur.

Thanks for your patience whilst this issue was ongoing.
Posted Mar 08, 2018 - 20:55 UTC