My video creation automation to instagram reels has been working for over 2 weeks without issue, posting every 5 hours. About 48 hours ago, I am now receiving this error that is typically for video format issues. However, as you can see below, the video format is supported (.mp4).
Nothing has been changed in my flow, video format is correct and I’m looking for help on this error that started happening out of no where. Utilizing json2video which should by default output the correct video format.
Checking in on this, anyone have any ideas?
iim facing same issue
it satrted around yesterday for me too
Glad to hear it’s not just me - would be great if we could get Make support in here to review.
+1 here, the same about 4d ago. Any news?
+1 here, I also faced the same error 4 days ago.
I’ve been having the same problem for 2 days. However, if I post reels manually through the Instagram app, everything works
Hello @here 
Can you please reach out to our Customer Care and submit a ticket? Provide all info as possible. Thank you very much. 
Just submitted. Hoping a fix will be implemented soon.
Hi, I am facing the same issue when trying to post an Instagram Reels. My video URL comes from a download link from Google Drive though. I haven’t had problems/errors until this time. Curious if anyone got a feedback from the ticket created?
I have a problem when uploading a video to Instagram, it gives the error “Error: Media upload has failed with error code 2207052”. I see that many people get it, but no one has been able to solve it. I’m trying to upload a video that I’ve previously uploaded through the service to Instagram. Then everything went well. This I write to the fact that the format of the video is suitable for Instagram and if I upload the same video manually, everything works out. Now about the format of the link. It has the following form: https://drive.google.com/uc?id=1Rc7H0Ubuk-ruMiXnf7ZtN5VfgOWSSUTE&export=download In idea, this is the right kind of link. Earlier the automation worked, but now it gives an error. I attach additional screenshots describing the problem.
I encountered the same error last week and I found that it was due to using a Google Drive. To resolve this issue, I recommend using other file hosting providers, such as Dropbox, that offer direct download links too. This approach ensures smoother and error-free access to the file.
Even I am facing this issue. First encountered on 2nd Aug 2025 1200 PM IST.
Anyone know any fix?
No response from Make yet - still waiting for them to respond to this widespread issue. I did submit a ticket a few days ago but no response either.
+1 here. My issue was also due to Google Drive download link and switching to DropBox resolve the problem.
Hello
Our Customer Care Team Agent has found that Make successfully sent the request to Instagram to process the file. But, after an “in progress” status, Instagram rejected it and responded with an error code 2207052. As per Meta’s documentation, the error indicates an issue with the file itself.
This issue mainly happens when you map the Google Drive URL. For some reason, the Instagram API does not take the image when the Google Drive downloadable link is passed.
In this case, the simplest solution would be to pass the image to an app such as cloud convertor. Map the Google Drive link into the URL field of Cloud convertor and select the output format, and name the file extension in the filename
This will generate a temporary URL as shown below, using which the file can be easily uploaded to the Instagram app. This should resolve your problem.
Please note that Make is sending the request and receiving a 200 status code in response. The rejection is coming from Instagram’s side, and Make does not have control over it.
If you need further clarification, I’d suggest reaching out to Meta support. You can also share the raw request and response details with them for investigation.
{
“response”: {
“status”: 200,
“headers”: {
“etag”: “"fde56ef069e83624b7c4c0e1295eabfd4fd93036"”,
“content-type”: “text/javascript; charset=UTF-8”,
“vary”: “Origin”,
“cross-origin-resource-policy”: “cross-origin”,
“x-app-usage”: “{"call_count":0,"total_cputime":0,"total_time":0}”,
“access-control-allow-origin”: “",
“facebook-api-version”: “v22.0”,
“strict-transport-security”: “max-age=15552000; preload”,
“pragma”: “no-cache”,
“cache-control”: “private, no-cache, no-store, must-revalidate”,
“expires”: “Sat, 01 Jan 2000 00:00:00 GMT”,
“x-fb-request-id”: “AYPR_QICwDHURVAoV7LLt4N”,
“x-fb-trace-id”: “Hc39ivTVjdG”,
“x-fb-rev”: “1025527266”,
“x-fb-debug”: “PtbyxUqpHOVc3Sgd53qVrP9snQAzQVs5WkOkPvuI1Tb/EsMj6CTSx+q8eSq7Gve1143WYtLC60mapKddmuJsTg==”,
“date”: “Tue, 05 Aug 2025 18:47:23 GMT”,
“x-fb-connection-quality”: “EXCELLENT; q=0.9, rtt=18, rtx=0, c=10, mss=1380, tbw=372, tp=-1, tpl=-1, uplat=87, ullat=0”,
“alt-svc”: “h3=":443"; ma=86400”,
“connection”: “close”,
“content-length”: “114”
},
“body”: {
“status_code”: “ERROR”,
“status”: “Error: Media upload has failed with error code 2207052”,
“id”: “17994706133667734”
}
},
“request”: {
“url”: “https://graph.facebook.com/v22.0/17994706133667734”,
“qs”: {
“fields”: “status_code,status”
},
“headers”: {
“user-agent”: “Make/production”,
“authorization”: "**”
},
“method”: “GET”
}
}
Hope this helps.
Per my original post, I am not using Google Drive, I am using the official make.com verified vendor json2video: https://www.make.com/en/integrations/json2video
Here is my flow:
I’m looking for a resolution for json2video and/or please provide documentation on how to work in the converter into this flow.
Did anyone check whether the CloudConvert workaround works? It usually does with feed (picture) posts on IG.
This might be nothing, but I’ve been trying to debug this issue and have a ‘good’ and ‘bad’ video. The ‘bad’ video didn’t post with the same error you all are getting. However, I added an error-handler in (The module doesn’t fail, but you can do an IF on the status = ERROR) and repeated the Instagram Post a second and third time - and now it posts.
This is highly speculative - but it “feels” like theres a cloud lambda function / serverless function that needs to get warmed-up to do the job and occasionally it fails. By trying a second time, the function is ready and can post.
Give it a go and see if it works, it might be rubbish, but worth a shot.
I’ll try this and report back - however it would be nice if Make could resolve this instead of providing workarounds, pretty frustrating. Thanks for the troubleshooting.
