The instagram carrousel module gives me a “Invalid user id (110, OAuthException) - Instagram for Business (Facebook login)” error.
It functioned fine before, but it started happening today on a scenario that has been running fine for weeks.
I’ve tried removing and recreating the connection. I tried removing it on the side of Meta Business suite, I tried removing it in my facebook account, and everytime recreating it.
The strange thing is that with the same Make connection, posting to the related Facebook page is no problem at all. It’s just Instagram which is refusing with the above error. Why is this giving me a user ID error, while with the same data, Facebook is working fine??
Error messages or input/output bundles
Invalid user id (110, OAuthException) - Instagram for Business (Facebook login)
Facebook may still work, but Instagram is stricter. That “Invalid user id (110)” error usually means the link between the Facebook Page and the Instagram Business account was silently broken or refreshed.
Recreating the Make connection won’t help much if that Page IG link is the issue. A quick check in Meta Business Suite to reconnect Instagram to the Page normally fixes it.
Hi Tony,
Thanks for your reply. I did indeed try this. Removed all links as well and recreated them in Meta Business Suite with no effect.
Strangely this error started from Monday. Before everything ran fine. Even the connection to the facebook page runs fine. It’s just the connected Instagram account that stopped working from one day to another.
Cheers,
Oki
Given that Facebook posting still works and the issue started suddenly, this really points to a Meta-side change affecting Instagram only. Meta often invalidates Instagram user IDs or access scopes independently of Facebook, even when they’re linked to the same Page.
At this point, re-linking accounts and recreating the Make connection usually won’t resolve it. What typically fixes this is re-authorizing Instagram access at the Meta app / permissions level, or waiting for Meta to fully propagate a backend refresh (this can take 24–48 hours after changes).
If it persists, I’d recommend opening a ticket with Meta support and referencing the Invalid user id (110, OAuthException) for Instagram Business. Make is successfully authenticating (since Facebook works), but Instagram is rejecting the user context.
Unfortunately, this is one of those cases where nothing actually changed on your side — Meta just tightened or reset something in the background.
Update: It seems to only happen to certain posts I pull out of Airtable. Others are fine! The plot thickens!! Why do some posts trigger an error and others don’t.
It seems it is not on the Meta side (completely), and maybe also not on the Make side.
Some posts trigger the 110 error, others trigger a 9007 error, yet others trigger a “media not found” error.
Yet all are made in exactly the same way: Images are edited in Cloudinary and uploaded to Airtable, from where they are picked up by Make to be posted to Instagram.
All in the exact same format, all with the exact same number of pictures in the same dimensions, with almost identical text. I’m a bit at a loss of why it does not give consistent results.
If only some Airtable records fail, it’s most likely a media issue rather than an authentication problem. Errors like 110, 9007, or “media not found” usually mean Instagram can’t properly access the image. Even if all posts look identical, one image URL may not be fully available.
This can happen if the URL isn’t truly public, if the Cloudinary link expires or redirects, if there’s a temporary availability issue, or if there are small differences in file metadata.
I’d suggest comparing a working image URL with one that fails and opening both in an incognito browser to confirm they load instantly.
This points more to Instagram media validation than to Make or permissions.
What is your goal?
What is the problem & what have you tried?
Error messages or input/output bundles