20
Re-triggering Zaps
under review
Plinio Averbach
Why Zap and not a Make/Webhook?
Zapier is to costly!
J
Jennifer Van Kirk
+1 please. This would save time and avoid having to manual enter info when there is a zap issue.
C
Colleen
Yes, please, this would save time when an error occurs. Thank you.
Jon Waldstein
under review
Brandon Randall
Please. Please. Please!
Jessica Thomas
in progress
Ben Meredith
under review
When a Zap fails to trigger, it's often a result of something preventing background queued processes from firing on the site in general. Here's the long version of why that's a tough issue to combat:
In the donation process, we limit the number of synchronous things that happen to those things that actually move the transaction through. Other actions and processes are essentially put into a queue to run after the fact. That's intentional, because the donation is the main priority.
So when a queued process doesn't happen, it's hard to isolate exactly
why
it didn't happen. The next best case is to be able to manually trigger the process. So this feature request will solve two problems for the price of one. I'm escalating it to the team.
Ben Meredith
Merged in a post:
Enable option to retrigger zaps
Rick Alday
Sometimes zap trigger before all payment data has been received from the gateway.
Video from customer: https://www.loom.com/share/a187c3811aa346e8941923ccc3395cb9
The zap should trigger until all data has been received or we should have a way to re-trigger the zap