My scenario was working fine until September 20 and suddenly started failing on the 26th with the error Media ID is not available (9007, OAuthException) when posting on Instagram.
The flow is Canva - Export a Design (PNG) / Instagram for Business - Create a photo post. Facebook posts with the same Canva export still work, but Instagram now rejects it.
I already reauthorized both Canva and Instagram connections in Make, but the issue persists. Has anyone else experienced this recently? Did Instagram change something about accepted URLs in the past few days? Any ideas for a workaround would be great.
I did not test it, but when I started building Instagram automation yesterday, I read that the ‘Create Photo Post’ module for Instagram only supports JPEG (see screenshot). It looks like you are exporting a PNG.
Other option: As I was having trouble getting this to work, I checked the error codes: “9007: The media is not ready for publishing. Please wait a moment.” Maybe it’s a timeout?
I had trouble getting the photo from a public Seatable URL. I found a tip in this forumregarding posting videos to Instagram: use the 0Codekit module to generate a temporary URL. This worked fine for me. However, I do not understand why Seatable did not work, even when I handed over a public WordPress media library URL. Below you see my workaround.
Thanks a lot for your reply earlier! Your note about the JPEG format was really useful and I switched my Canva export from PNG to JPG.
At first, I still got the same Media ID is not available (9007, OAuthException) error on Instagram, but then I tried adding a simple HTTP module right after the Canva export (without changing anything else in the Instagram step)… and suddenly it worked!
So it may look like the extra HTTP call “cleans up” the Canva export URL or the way the file is delivered, and Instagram is finally able to fetch it.
Hopefully this helps anyone else running into the same issue. Thanks again for pointing me in the right direction!
Just to make sure I understand correctly. You put an ‘HTTP make a request’ module between Canva and Instagram. The input for the HTTP module was the Canva URL, but you still used the Canva URL as the input for the Instagram module. Am I right?
Yes, that’s correct. I added an HTTP “Make a request” module right after the Canva export, using the Canva URL as input. I didn’t change the mapping on the Instagram module (it’s still using the Canva export URL).
It looks like just having the HTTP request in the flow makes Instagram accept the Canva URL again. Without that extra step, I still get the 9007 error.
Not sure why it works this way, but it solved the issue
I’m getting the exact same problem since this monrning. My scenario has been running completely fine for over a year until now. I’m pulling .png files from Airtable.
@Arnaud4 can you specificy what the exact solution was? Was it the change to .JPEG or the HTTP request? If the latter, what did you specifically do?
Hello. I’ve been having the same problem for a few days. After reading this thread, I tried adding an “http get a file” module just before the Instagram module and it seems to work. Note that in the Instagram module I did NOT change the Photo URL parameter with an output from the http module. This is very strange and it costs an extra operation for nothing.
Yes, it works the same for me, but 2 days later the error is present again. This is not the solution.
Even the 0codeKit solution, i don’t know what to do
Yep, same issue persists for me, tried all workarounds mentioned in this thread. And eventually, yesterday I managed to fix the bug by removing the filter and adding it back. Today I have the same bug back. Not good -.-
