We have multiple newly created zaps and an older zap that are all turning off automatically. No errors show when we testing the zap. We are on a paid Pro plan. Not all of our older zaps have started turning off but we fear this is going to start happening if we edit those at all.
Page 1 / 1
Hi
For us to have more context, we would need to see screenshots with how your Zap steps are outlined and configured, thanks.
Check your Zap app connections here: https://zapier.com/app/connections
Check your Zap > Change History for more context.
My hunch is the issue is related to the Zap trigger app, since that is the common app across your Zaps.
I recommend working with Ruby Support to troubleshoot their Zap app integration.
Will talk to our dev team, but ultimately, I don’t get why current zaps keep working but new won’t work. If we edit an older, the same thing starts happening where it turns off automatically. Havent been able to get ahold of Zap support either.
There may be an issue/limit with the # of Zaps that can be connected to the Ruby app for the connected Ruby account/API key.
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.