Media upload has failed with error code 2207052 (Instagram reels)

Questions
21

I will also try and report back here

22

So unfortunately this isn’t really working for me and also I think there is an inherent flaw.

I see that you are not utilizing “fallback” which will only attempt the 2nd route if the 1st fails, so you are opening yourself up to duplicate posting if any of the 1st or 2nd attempts go through.

In addition, Make.com is not recognizing this error, so fallback does not even work as intended, as it won’t attempt the fallback route due to not knowing there is an error. Yes it says “error” in the status_code but it’s not recognizing it as an error in the router or even in your scenario history:

image
image1403×1023 107 KB

Scenarios are considered successful when in fact they are not:

image
image1729×143 7.92 KB

23

Alright I heard back from Make support on my ticket and they just suggested CloudConvert again so I gave it a go. As long as you don’t need more than 10 link conversions daily this should be a zero cost solution, otherwise you need to pay CloudConvert. Ultimately I think the root issue is with either json2video or facebook/instagram not aligning correctly on formatting even though the format hasn’t changed.

Essentially what you’re going to do is run your original Video URL that was going straight to Instagram through CloudConvert. File name for your output is not important (burnie.mp4 in the example below), can be anything but just make sure it ends in .mp4:

image
image573×1298 57.8 KB

I just made sure this convert step was as early as possible in my scenario after getting the video URL so that the converted link would always be available on the final step of upload to Instagram.

Now since you are using a new URL generated from CloudConvert, your final step is to replace the Video URL in your upload step to the “temporary URL” object from your CloudConvert step:

image
image580×527 35.6 KB

This workaround fixed it for me, good luck. BTW if you’re into crypto or low cap memes, come check @earnwhileyouafk out on X, we are building automations like these videos around a deflationary token for free 24/7 organic marketing to grow our market cap.

3 Likes
24

CloudConvert workaround worked for me. However be careful, cause by following above guideline the video will be always reprocess by CloudConvert. In my case, I want it to stay away from changing my video, so I implemented the set video_codec to "copy" and audio_codec to "copy", so it only rebuilds the container without touching the streams.

25

Just checking in. Any fix by Make on this yet?

26

Using JSON2Video too. We fixed it by saving the video file from J2V to an FTP server, then upload to IG from there.

27

That’s definitely frustrating, especially since it was working fine for weeks. Even if the file extension is .mp4, Instagram can still reject videos if something in the encoding (codec, bitrate, frame rate, audio track, etc.) doesn’t meet their requirements.

A few things you could try:

  1. Run one of the failing videos through a tool like MediaInfo or HandBrake to confirm it’s using H.264 video codec and AAC audio codec, which Instagram prefers.

  2. Check that the file size, resolution, and duration are still within Instagram’s limits — sometimes small changes in source material can push a file just outside their accepted specs.

  3. If you can, try manually uploading one of the same videos to Instagram to confirm whether it’s an API-specific issue or a formatting issue.

  4. Since json2video generates the file, it might be worth forcing a specific export preset that locks in Instagram-safe settings, even if it was working before.

Sometimes platforms quietly update their ingestion rules without notice, so revalidating against the latest Instagram specs can help pinpoint the problem.

29

Has Make been able to fix this yet?

Don’t wanna try other alternatives shared in the thread, too much hassle.

30

CloudConvert is the only known solution, if you’re having trouble just let me know and I can help. It really does not take much time to do.

31

This worked for me. Thanks!

32

Hi All, Thanks just wanted to say this post gave me the direction i needed to fix this issue.

I have a different solution to cloud convert. i’m using 0codekit to upload the file to a temp url, this way i don not need to change the video in any way. There is a free level for 0codekit for a zero cost solution

1 Like
33

Hi guys! Thanks for post. This is exactly what Iwas going through yesterday. It was just a never ending loop. So with CloudConvert and temporary file, do we still need DropBox?

34

lamentavelmente acontecendo a mesma coisa comigo, o google drive, um sistema que funcionava hå mais de 4 meses, parou do nada, e o suporte da make.com ainda nao apresentou uma soluçao definitiva para que processa vårios vídeos por dia vai ter que pagar, ao usar o cloud convert, mas uma ferramenta para incluir no orçamento.

35

Just wondering if you found a solution for this issue. Im experiencing the same. (Media upload has failed with error code 2207052)

36

Hello :waving_hand:

We’ve looked into the error you encountered and found that this error (code 2207052) can occur for several reasons - for example, if the file is in an unsupported format, exceeds Facebook’s size limits, becomes corrupted during upload, or if Facebook has not yet finished its internal processing when the status is checked.

In many cases, this issue happens when the file format or size doesn’t meet Facebook’s requirements, or when the platform simply needs more time to finish processing the media. To help avoid this, we recommend checking that your file is in a supported format (such as JPEG or PNG for images, or MP4 for videos), within Facebook’s allowed size limits, and that the correct file type is indicated when uploading.

If the error comes from Meta, please contact them directly. :folded_hands:

37

After 2 days of trial and error, I finally got Publit.io to work with Make. Setup was a bit tricky at first (Publit requires timestamp, nonce, and a SHA-1 signature), but it worked in the end.

I had tried CloudConvert too, but the 10 conversions/day limit wasn’t good enough for my use case.

Here’s the config that worked for me:

HTTP Module Settings

  • Evaluate all states as errors (except for 2xx and 3xx): Yes

  • URL:

    bash

    CopyEdit

    https://api.publit.io/v1/files/create

  • Method: POST

Headers

  • Accept: application/json

Query String

  • api_key: <your_api_key>

  • api_timestamp: {{formatDate(now; "X")}} ← current Unix timestamp in seconds

  • api_nonce: 63528192 ← any random 8-digit number (must be unique per request)

  • api_signature: <sha1(api_timestamp + api_nonce + api_secret)>

Body type

  • multipart/form-data

Fields

  • file = (File) → e.g. HTTP – Get a file module output, or you can use file_url instead

Parse response: Yes

38

Hi all,

I managed to solve this by adding the Cloudinary Upload a Resource module between Google Drive Get a Share Link module and Instagram Create a Reel Post module.

Hope this helps,

Riccardo

image
image1922×566 62.7 KB

39

Here is the solution: https://www.youtube.com/watch?v=B6IN7wa1z18

40

This didn’t work for me. I used CloudConvert that didn’t work as well.

41

This worked for me too, thank you so much