Video is too large to process synchronously, please use an eager transformation with eager_async=true to resolve

Hong Li

February 07, 2020 22:06

Video is too large to process synchronously, please use an eager transformation with eager_async=true to resolve

I'm getting the error above, even though I've set eager_async=true in my request. Below is a dump of my request, I've blanked out signature and key. I am also used chunked uploading passing the same parameter for each request.

Headers

POST /v1_1/[OUR CLOUD NAME]/video/upload HTTP/1.1
Host: api.cloudinary.com
Connection: keep-alive
Content-Length: 3637218
Content-Range: bytes 168000000-171636549/171636550
X-Unique-Upload-Id: 1581111537930
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.117 Safari/537.36
Content-Type: multipart/form-data; boundary=----WebKitFormBoundaryXwlxQVLO1DUHDLqh
Accept: */*
Origin: https://oursite.com
Sec-Fetch-Site: cross-site
Sec-Fetch-Mode: cors
Referer: https://oursite.com/
Accept-Encoding: gzip, deflate, br
Accept-Language: en-US,en;q=0.9

Form Data

file: (binary)
eager_async: true
timestamp: 1581111531735
signature: OUR SIGNATURE
api_key: OUR KEY

0

• 

  Aleksandar Kostadinov

  February 08, 2020 13:07

  Hi Hong,

  This specific error is usually returned in a few scenarios. For example, if you are performing eager or on-the-fly video transformations synchronously for videos larger than 40MB on the Free plan or 100MB on any paid ones. Alternatively, you will receive this error if you are requesting an incoming transformation synchronously for any video above the mentioned limits. In your case, based on looking at the form-data parameters, the most likely reason for this error is that you have an incoming transformation in a default upload preset which is attempting to transform this large video synchronously. eager_async is only relevant if you are performing eager transformations and it has no effect on incoming transformations.

  May I please ask you to check your account if you are using any default upload presets? You can see that if you go to the Settings -> Upload tab of your account and scroll right at the bottom. If you are using an upload preset with an incoming transformation then you would need to either configure the preset to perform the incoming transformation asynchronously or you will need to include the "async" parameter set to 'true' in your form data, instead of eager_async.

  Please let me know how it goes.

  0

Post is closed for comments.