김수빈
Subin Kim

Two AI Models Called It a Meta Bug. It Wasn't.

Review No. 718

Everyone who builds with AI ends up with a favorite model. Claude for writing and browser work, GPT for code and architecture: pick your poison. The trouble starts when your favorite hits a wall and your second opinion agrees the wall can't be moved. At that point it feels reasonable to declare the problem unsolvable and go write an angry forum post.

I nearly did exactly that this weekend.

Connected, allegedly

I recently built up social media automation for my online magazine. It publishes Instagram carousels automatically through Meta's official Graph API. Paying a third-party scheduler for something Meta offers for free seemed silly. The setup should have been dull, and on paper it was:

  • A valid 60-day System User token.
  • Issued by the right Meta app under the right business portfolio.
  • Carrying exactly the three permissions we needed: instagram_basic, instagram_content_publish, and instagram_manage_messages.
  • And in Meta Business Settings, a Connected apps screen stating plainly that my magazine app had access to its Instagram handle.

Then our code asked the API the most basic question available: which Instagram accounts are assigned to this token? (/me/assigned_instagram_accounts). Meta answered with an empty list. Querying the Instagram account directly got an HTTP 400: "Unsupported get request."

The dashboard said connected. The API said we owned nothing. Both couldn't be true, and Meta wasn't going to tell us which one was lying.

Two days of doing everything right

GPT Astra and Claude Opus 5.5 approached it the way a conscientious engineer would. They believed the label. Meta's token debugger called our token "type": "SYSTEM_USER", so both assumed it was an ordinary system user still waiting on its Instagram grant. Over two days they worked through the list:

  1. Wrong Instagram ID? Ruled out.
  2. Did whoever clicked Authorize lack full control of the Instagram account? We upgraded the admin to full control (Everything) and generated a fresh token. Empty list.
  3. A stale connection record? We removed the magazine Instagram handle from Connected apps, ran the Unified Login flow from scratch, and saved a brand-new token. Empty list.

Both models then reached the same conclusion. This was a delegation bug on Meta's backend, nothing more could be done locally, and here was a tidy bug report for the Meta Developer Community forum. It was thorough, well reasoned, and, as it turned out, wrong.

The question nobody asked

Usually I'd call it a day and find another route to do the work I imagined. But this time I somehow thought maybe Gemini 4 Argon could solve this although my brief experience with Argon was not too great—come to think of it, it's mostly about the harness that is Antigravity, which requires a lot of polishing and improvement compared to Codex and Claude Code.

I half-believingly handed the same handoff document to Gemini 4 Argon. It didn't suggest a fourth run through the login wizard. It asked what kind of SYSTEM_USER /me was actually pointing to.

There are two kinds, it turns out, and /debug_token labels them identically.

The first is a hidden business integration system user. Meta quietly creates one when you generate a token through the Facebook Login for Business OAuth flow. That flow exists for B2B onboarding, such as an outside agency's app asking a client's portfolio to share its Instagram account. Our portfolio owned both the app and the Instagram account, so we had been onboarding ourselves as our own client. Meta recorded the connection in the UI and then, without comment, declined to delegate same-portfolio assets to the invisible user. Because that user is invisible, it doesn't appear under Business Settings > Users > System users, so you can't assign it anything by hand either.

The second is an explicit portfolio system user. This is the first-party mechanism for a company that owns both the app and the account. You create it directly under Business Settings > Users > System users. In our case, that page still read "No system users added yet."

The fix took under five minutes:

  • We created a portfolio system user under System users.
  • We used Assign assets to give it full control of the magazine app and its handle.
  • We generated a 60-day token with the same three permissions and updated our verifier (verify_meta.py) to check portfolio SystemUser nodes directly against the business and Instagram endpoints.

We ran one probe. Profile: 200 OK. Publishing quota: 200 OK (0/100). Business: 200 OK. No blockers, and a slightly humbling number of green lights.

What this is not

It would be easy to file this under "Model A beats Model B." It isn't that. GPT Astra and Claude Opus 5.5 did the unglamorous work of eliminating bad IDs, permissions, and stale grants. They left an evidence trail clean enough for a fresh pair of eyes to see past it. Without that work, the problem would have stayed murky.

But both stayed inside the frame we'd handed them. They asked how to make the OAuth wizard work. Gemini 4 Argon asked why we were using a client-onboarding wizard on our own account at all.

So the lesson isn't "use Gemini." It's that frontier models have different blind spots, and two of them agreeing is not the same as being right. When your go-to models tell you the problem is on the vendor's side, get a third opinion before you file the bug report. The vendor's bug may turn out to be yours, and five minutes long.