Issue uploading long Zoom recordings to Vimeo via Make – Incomplete or stuck upload

Features
, ,
1

Hello,

I’m encountering an issue with an automation in Make that retrieves Zoom recordings, filters the video file, and uploads it to Vimeo.

:wrench: Scenario structure:

  1. [Zoom] Watch Recordings – triggers when a new cloud recording is available.
  2. [Iterator] – iterates over the recording files.
  3. [Zoom] Download a Cloud Recording – downloads only the video file (filtered by File Type = MP4, see attached screenshot).
  4. [Vimeo] Upload a video – uploads the video to a Vimeo account.

image
image2227×732 64.4 KB

:cross_mark: Problem:

When the Zoom recording is longer than one hour, the “Upload a video” module appears to work successfully in Make, but:

  • On Vimeo, the video remains stuck in “Upload pending” status.
  • An error is displayed on Vimeo:

“A problem occurred during upload. Please try again.”

  • The video is never processed or visible, as if the upload is incomplete or corrupted.

image
image1771×1870 104 KB

Here’s what I’ve checked:

  • The Vimeo OAuth connection in Make was recently reauthenticated and is working.
  • The file downloaded from Zoom plays fine locally (the video is intact).
  • The scenario works perfectly with shorter Zoom recordings.

:white_check_mark: Question:

Does Make impose any file size or duration limits when uploading videos to Vimeo through its module?
Is there a recommended way to handle large or long video uploads (1 hour or more) to avoid this Vimeo upload failure?

Thanks in advance for your support :folded_hands:

2

If you have the Make DevTool Chrome extension installed, you should be able to view the request and response headers and body from each module when you manually run the scenario.

From the Help Center article about the Make DevTool:

Make DevTool allows you to debug your Make scenarios in a completely new way. It adds an extra pane to the Chrome Developer Tools. Using this new debugger pane, you’re able to check all the manual runs of your scenario, review all the performed operations and see the details of every API call performed. It also brings a whole bunch of new opportunities for Apps development. You’re able to check every call that your app has performed. Thanks to this extension, you can easily debug your scenario, see which module, operation, even which single response causes the error, and then get your scenario back on track. Try it out and let your scenarios shine!

For more information on how to install and use this, see https://www.make.com/en/help/scenarios/integromat-devtool

Once you have more details like a return code, you can check what it means here: https://developer.vimeo.com/api/upload/videos

Hope this helps! Let me know if there are any further questions or issues.

— @samliew

P.S.: Investing some effort into the Make Academy will save you lots of time and frustration using Make.