Skip to main content

Hey,

My zapier automation keeps turning off and I’m getting the following error message: Task was stopped because its Zap was turned off during its execution.

I believe it’s related to the cloud convert action I have in the automation. We pay for Cloud convert and have barely used our subscription. 

Zaps are being triggered at the same time, could it be an issue with overloading clouconvert with too many tasks at the same time? How can I delay tasks so they only run once the previous zap was complete?

Thanks

Hi @jasonpotter 

Successive Zap Run errors can cause the Zap to automatically turn OFF.

For us to have more context, post screenshots showing:

  • the encountered error
  • how your Zap steps are outlined and configured in EDIT mode

Hey @Troy Tessalone 

I’ve attached what you asked for, let me know I can need to provide any more information :) 


@jasonpotter 

You can try adding a Delay (After Queue) step to space out the Zap Runs: https://zapier.com/apps/delay/help

 

You may also want to try using an Airtable View with Filters in the Zap trigger step to limit which records trigger the Zap to run.

 


That seems to have fixed the problem! Thanks Troy

 


That’s awesome @jasonpotter! A huge thanks to Troy for pointing you in the right direction!

If you have any other questions, please don’t hesitate to reach out to the Community. We’re always happy to help! 🤗


Reply