How do you catch a Zap that silently stopped?

Hi ​@Vasco_Builds, welcome to the Community! 👋

Was it an instant or polling type of trigger that failed to run?

With polling triggers anything that’s missed usually gets triggered on the next time the Zap successfully “polls” the trigger app and finds new items. With instant triggers, the Zap relies on the app sending over the information to trigger it. You could in theory keep a record of the items that trigger the Zap in something like Zapier Tables. And have another Zap trigger on a regular schedule, use a search action or make GET request to find the more recent item, then search the records in the table to see if it’s there and alert you if it’s not.

But if the trigger app isn’t sending anything due to API changes or incidents on their end, I wonder if it might be more effective to sign up to email alerts on the trigger app’s incident page so you’re alerted whenever there’s a potential issue. You can then have a Zap keep an eye on your inbox for those types of emails, use an AI by Zapier action to determine if it might affect a Zap triggering and send you a notification by SMS so you can check the Zap.

And you can use an app like Wachete that keeps an eye on multiple web pages (like the trigger app’s API changelog or deprecation notices page) and have the Zap alert you by SMS, by email etc whenever there’s any updates to those pages that might affect the Zap.

Hope that helps. If you give any of that a try and get stuck just let us know!

Hi ​@Vasco_Builds 

If app connections expire in Zapier, then you should get an email notification.

If something happens outside of Zapier, then it probably has to be monitored elsewhere.

Make sure to subscribe to notifications from app status pages.

e.g. Zapier Status page: https://status.zapier.com/