Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

I’m running into an issue where my Zap turns off by itself. It doesn’t show any errors in the immediate history, so I’m not quite sure what to do, I have to login every month and double-check it’s ‘on’ and most of the time to manually turn it ‘on’.

I’m using the free version so maybe that’s why it’s turning off by itself?

Article: https://zapier.com/help/manage/organize/manage-your-zaps

Zapier automatically turns your Zaps off for you in 2 situations:

  • You lose access to a paid feature the Zap uses (e.g., multi-step Zaps or premium apps) due to a trial expiration or plan downgrade.
  • Multiple errors occur each time the Zap tries to run. An email notification will be sent if a Zap is turned off due to errors.

You can use the Zapier Manager app to configure a Zap that alerts you when another Zap turns OFF.

Article: https://zapier.com/apps/zapier-manager/integrations#triggers-and-actions

 

Hi @Lir ,

Circling back to make sure you are sorted with this Zap! Did Troy’s resources above help you resolve this? 

Our Zap keeps erroring out and the Error says “Task was stopped because its Zap was turned off during its execution.” We turn on the Zap (again - it keeps turning itself off), then run the history again and it shuts itself off and says “Task was stopped because its Zap was turned off during its execution.” It ran for a minute about 2 hours ago and now won’t run the load.

 

  1. Turn it on, good.
  2. Run the history, error.
  3. Error? Yeah, it errored because it was off.
  4. Off? Yeah, that happens when it runs into errors.
  5. What were the errors? It was off.
  6. Return to Step 1 and repeat until you’re properly hitting your head on desk.

 

Hellllp. lol

@Protocol Thats a tough situation. 

Have you tried duplicating the zap and using the clone rather than the original?

Terms & Conditions