Troubleshooting Bubble actions returning “Not found” errors in Zapier

Hi ​@Johnny Pelegrini 

Probably best to report this issue via a ticket to Zapier Support: https://zapier.com/app/get-help

One thing worth ruling out, since Postman works and Zapier doesn't: check which Bubble version the Zapier connection points at. If the connection was set up against the development version (version-test) and your IDs come from live, every Update Thing returns "Not found" even though the record exists. Postman would succeed because you're hitting the live URL directly.

Two other things that produce the same error:

• Privacy rules on that data type. Your Postman call may use the admin API token, while the Zapier connection runs under different credentials that can't see the record. Bubble then responds as if the record doesn't exist.
• A recent deploy that renamed the data type. Zapier still sends the old type name in the URL.

If none of those fit, opening a Support ticket with the run ID is the right next step, as Troy said.

Thanks ​@Troy Tessalone and ​@farahnas1.

I've talked to Bubble's support as well and the issue is on their side. It's still not fixed, but at least now I know where is failing. Thank you both. 

Quoting them:

Hello, this is Dexter from Bubble Support. Thanks for reaching out, and we apologize for the inconvenience caused. We've confirmed that your app is being impacted by an ongoing incident, which you can track on our status page.

Our engineering team has identified an issue affecting platform availability and will be making a series of infrastructure changes to resolve it.

Some disruption is expected while that work is underway, including pages failing to load, workflows timing out, and brief periods where your app is unreachable. Behavior may improve and then recur as changes are made.

We know this will be disruptive and we apologize for the impact.

Our engineering team is actively working toward a resolution, and we'll be in touch as soon as we have further updates to share.