Skip to main content

Hi,

I have a Zapp set up between Plug&Pay and Billit, but for some reason, it keeps turning off automatically. There are no error messages, and when I check the app connections, everything appears to be in order.

Do you have any idea what might be causing this? Any insights would be greatly appreciated.

Thanks in advance!

Hi ​@zpeeters 

Check the Zap Change History for clues: https://help.zapier.com/hc/en-us/articles/23975937613069-Easily-review-your-Zap-s-change-history-from-within-the-editor


Hey ​@zpeeters, just checking in—were you able to get any insight from the Zap Change History as to why the Zap keeps being turned off?

If not, have a look through our Can't turn on or publish Zap guide to see if one the issues mentioned there could be the reason. 

Keen to ensure this gets sorted so let us know if you still need any help! 🙂


Hi,

There are a few possible reasons why your Zap between Plug&Pay and Billit keeps turning off automatically, even though there are no error messages:

  1. Zapier's Autoturn-off Feature: If a Zap is inactive for a long time or runs into repeated issues (even if they are temporary), Zapier may turn it off automatically. Check your Zap History to see if any runs failed.

  2. App Connection Timeouts: Even if the app connections appear fine, they might be expiring or disconnecting intermittently. Try reconnecting Plug&Pay and Billit in Zapier and reauthorize both apps.

  3. Zapier Plan Limits: If you are on a free or lower-tier Zapier plan, there could be a limit on how many tasks your Zap can run. If you exceed your plan's limit, Zapier may disable the Zap.

  4. Rate Limits from Plug&Pay or Billit: Some apps enforce rate limits, which could prevent Zapier from executing actions. If you’re sending too many requests, the API might be temporarily rejecting them, causing the Zap to turn off.

  5. Zapier Bugs or Glitches: Sometimes, Zapier itself might have a bug. Try duplicating the Zap and running it as a new instance to see if the issue persists.

  6. Internal Logic or Filters: If you have filters or conditions that rarely meet the criteria, the Zap might not trigger often enough, leading Zapier to assume it's inactive and disable it.

Recommended Actions:

  • Check Zap History for any silent failures.
  • Manually reconnect both apps and test connections.
  • Ensure your Zapier plan limits aren’t exceeded.
  • Look for rate limits in Plug&Pay and Billit documentation.
  • Duplicate the Zap and test a new version.

Let me know if you need further troubleshooting!


@SamB ​@Troy Tessalone In the zap change history the only thing visible is that it immediately turns off after turning on. I got the tip from a collegue to try and recreate the zap to see if a new one will fix the issue, so will be trying that today.


Hi ​@zpeeters,

 

Just keep us on the loop so we can assist you further if needed. Thank you.