Hello @here 
Thank you for keeping the discussion active!
Unfortunately, as the issue originates on Meta’s side, there is nothing our devs can do on our end.
Please follow the discussion in the Meta Developers community.
Thank you for your understanding and patience 
It seems that there is no such similar issue in n8n.
No idea how we can solve this issue in Make.
Hey everyone,
I’m jumping into this thread because I’m honestly getting quite frustrated that this issue is still not properly resolved.
I’m getting the same error:
Media ID is not available (9007, OAuthException)
What really bothers me: I’ve built the exact same process in n8n, using the same Instagram account and very similar logic, and there it runs without any problems. That makes it very hard to believe this is “just Meta being unstable” – it really feels like something in Make’s Instagram module or handling of the API is off.
The painful part is:
I have a lot of active client workflows running on Make that rely on the Instagram module. Migrating all of these to another platform is absolutely not something I want to do, especially when this should be a stable, production-ready integration.
Right now my only “workable” hack is this:
I put a Break / iterator with 5 attempts in front of the Instagram module to basically “retry” a few times.
With this, the scenario runs successfully in maybe 90% of cases and the post goes through.
But I still need to manually check whether the post was actually published or not, which is simply not acceptable for client projects at scale.
So from my side, this is a serious reliability issue.
Could the Make team please:
Acknowledge clearly whether this is a known problem with the Instagram module itself (and not just “Meta being Meta”), and
Provide either
a proper fix, or
an official, reliable workaround (not just “try again and hope it works”)
At the very least, a transparent update on what’s going on and what the plan is would be really appreciated. Right now it feels like we’re all building production workflows on top of something that randomly fails with no clear resolution in sight.
Thanks in advance, I really hope this can be addressed with priority, because switching all my client automations away from Make just because of this one module is the last thing I want to do.
I would have to agree with you on this @Thomas_Obereder in this thread we have simply been told to keep an eye on the Meta Forum to check for any updates
Which I don’t believe is acceptable, especially when you hear that n8n is working fine.
Tonight for the first time in over a month the automation has worked and I have been able to post to 9 different accounts in one automation - with no issue
I am grateful that it is now working, but very worried for how it will be dealt again in the future if it was to happen again
Jumping in here as well. I’m experiencing the same (9007, OAuthException) error very consistently.
In my particular case, the behavior I’m seeing is that one execution works fine, but the next one fails; then it works again, and the next one fails.
This forces me to constantly review and manually re-run the pipelines that fail, which takes away a lot of the value of the automation.
I understand that Meta’s API can be unstable, but the point @Thomas_Obereder mentioned (about it working on other platforms) suggests there might be an improvement that can be implemented on Make’s side.
It would be extremely helpful if the @Make team could consider adding automatic retry logic directly inside the Instagram module itself. Perhaps if the module detects this 9007 error, it could automatically retry the post 2 or 3 times before reporting the final error.
This would save us a ton of manual work and make the integration much more reliable for everyone.
Thanks to the team for looking into this!
I spoke too soon, after success yesterday, I have now had the error Media ID is not available (9007, OAuthException) appear again
Does the team have any update on Make’s issue, as I’ve been told by several people that n8n modules are working fine?
We are experiencing this issue as well randomly. Rerunning the module that initially fails almost always works too, however not feasible to do at a large scale.
Same issue here. Media ID is not available (9007, OAuthException), using CloudConvert was working as a solution for me. But no longer is.
Tried to use Break, but it also doesn’t seem to be retrying given the settings (kindly) supplied by other users and still fails.
Just checking in to see that everyone is still being left in the dark by support?
it’s the meta graph api issue- we should all go to meta developer forum so meta would take their s*** together.
Please go upvote the BUG HERE https://developers.facebook.com/community/threads/812993571235767/
Sorry have just seen this, and at the moment its not again no for some reason. Im back here seeing people are still having the same issue which is insane. Am retracing my steps and seeing if im seeing anything different to others or new, but looks like same issue. I thought it be because ive not used the system for a few days but ive re-auth FB and IG and getting the image error still - 36001. Will update if i fix. hope you guys get it fixed!
update here to get news on this. i try all also, cloudinary, Ocodekit.. same error
Hi
A simple workaround worked for me:
First, add the image using the Facebook (Create a Photo Post) module,
then map that image (Media ID) in the Instagram for Business module.
Since then, the error disappeared, and posts have been publishing normally again.
It seems that Instagram now requires the file to be hosted within the Meta ecosystem (via Facebook).
thanks it is working for me as of now.
Hi, I know it works — I had this problem for 3 months and kept searching non-stop for a solution. Yes, this fix really works! I recommend my company — we create AI automations. We don’t have problems, only situations to solve. Glad I could help — best regards, CEO Darius FeuAI
Can you Show me how you configurate “get a completion”?
What is your goal?Solve this issue of “Media ID is not available (9007, OAuthException)”
What is the problem & what have you tried?i am automating instagram posting, but since last week i am facing this issue of : “Media ID is not available (9007, OAuthException)”.
but this works sometimes sometimes it doesnt what to do? i tried adding break module but it needs incomplete executions to be activated which causes same post to be posted multiple times, so had to remove the break module but this issue persists now what can be done?
Error messages or input/output bundlesMedia ID is not available (9007, OAuthException)
Screenshots (scenario flow, module settings, errors)this works most of the times, but it also posted same post multiple times, how to avoid this? the reason is because i think in the incomplete scenarios also get run every time my automation of posting on insta works thats why this issue is there, please guide if you know any solution to this. thanks.
this works most of the times, but it also posted same post multiple times, how to avoid this? the reason is because i think in the incomplete scenarios also get run every time my automation of posting on insta works thats why this issue is there, please guide if you know any solution to this. thanks.
All in all the two “solutions” that seem to be most reliable so far are to upload the image to facebook first and use that to create the instagram post, and/or to add a break error handler to keep retrying the call until it goes through.
