When something didn't work and you want to know why rather than guess, the platform logs page is where the answer is. It records what was asked of Inrō, what Inrō did, and what Instagram said back.
Open it from your account menu: Profile → View platform logs. It's a Pro feature.
Three tabs, three questions
The page has three tabs, and which one you want depends on the question you're asking.
API & MCP
Every request made against your account through the API or the MCP server: what was called, with what, what came back, and how long it took.
This is the tab for "my script isn't working" or "my AI assistant said it updated something and nothing changed". Click a row to see the full request and response rather than the summary.
Automations
Every scenario and campaign run, together in one list. Filter by type, by status, or search for a contact.
This is the tab for "did this person actually get the message?" You can go straight from a run to the contact it was for.
API errors
Errors that Instagram or another connected service returned to Inrō. Each row shows which call failed and what the service said.
This is the tab for "publishing stopped working" or "insights never arrive", where the real answer is usually a permission Instagram is refusing rather than anything in your setup.
Reading an error
Click any row to open the detail. The useful parts are the message the service returned and the call that produced it. Meta's messages are terse but specific: a permission that isn't granted, a media id it doesn't recognise, a session that has expired.
⚠️ Credentials are removed from these records before they're stored, so a token never appears on screen even though the failing call carried one. You can share a screenshot of an error with support without exposing your account.
How long logs are kept
Logs are trimmed automatically after a few days. They're built for "what happened this morning", not for a permanent audit trail. If you need something from a log for your own records, copy it out while it's there.
🐾 Netsuke's Tips
When a customer says a message never arrived, go to Automations and search their username before changing anything. Nine times out of ten the run is there with a reason attached, and you save yourself rebuilding a flow that was fine.
Check API errors after connecting or reconnecting Instagram. A permission you skipped on the Meta screen shows up here long before you notice the feature missing.
If your own script and your AI assistant disagree about what happened, the API & MCP tab settles it: both go through the same log.
What's next?
Troubleshooting Automations & Campaigns for what to do once a log tells you what failed.
How to Fix Common Meta and Instagram Connection Errors for the permission errors you'll find in the API errors tab.
