Zapier Manager "New Halted Task" trigger not firing for halted Zaps
I am having problems getting a zap working that sends out an alert when any zap in a folder enters the “halted” state. The zap uses the “Zapier Manager->New Halted Task” trigger.
The folder being monitored has a zap that fails to find a Contact in Salesforce and enters the “halted” state, but no trigger in being fired in the “Zapier Manager->New Halted Task” zap.
This is an important feature to capture issues for our company when running zaps and I’d really like to get this working. Has anyone else come across a similar problem and what they did to get the zap working.
If the New Zap Error or Zap Turned Off triggers only run after a long delay, check if you have autoreplay enabled. These triggers will only run after all autoreplay attempts are completed.
For Send Alerts on Failed Trigger and Send Alerts on Failed Action, select Always or Only Zapier Manager Trigger/Action].
If you're on a Team or Company plan, the error notification will go to the user who created the Zap that errored. The notification is not sent to the user who created the Zapier Manager Zap.
I would love to hear any update on this, as our company has the same issue. I receive email notifications for new zap errors, but do not receive anything for new halted tasks. this means I need to manually check for these stopped/halted zaps every day to ensure our Salesforce database is up to date.
This fix is desperately needed in Zapier!
I would also like to hear about any progress on a fix for this. This issue has been around for years now without any information when it will be fixed. We are considering alternatives to Zapier now as we cannot manually check the status of all the halted tasks each day. This is an important feature and Zapier should be taking this issue more seriously.
Has anyone found a fix for this? I’ve gotten the “Zap turned off” trigger to work but the “New zap error” just doesn’t work at all.
Honestly shocked at how unclear the documentation + use of this is.
I'm experiencing exactly the same issue. This problem invalidates Zapier as a serious business tool in some kind of simple zaps where failed sync tasks lead to manual interventions, there is no way to alert to someone or trigger a corrective event.
@Troy Tessalone I would like to note that I am also affected by this issue.
I have been able to set up triggers successfully for Zaps Turned Off + Zap Error, but have not be able to trigger the Zap Halted Task.
For others, it’s important to know that you can only trigger ‘Zaps Turned Off + Zap Error,’ flows for Zaps that YOU own, if you are working in a team context.
