Trigger fires but action step never completes, no error in task history

Hi and welcome to the Community ​@Adilbabu! 😁

It could be something like the structure of the trigger data changing and that’s causing a filter to now stop the Zap when it shouldn’t, or an issue with one of the actions in the Zap not surfacing an error correctly. Though it’s a bit hard for us to give advice specific to your situation or suggest a reliable fix without having more context on the setup of the Zap workflows and apps involved. 

Can you share a bit more detail about the Zap workflows and screenshots of their current setup? Screenshots also showing the Data In and Data Out from some recent Zap runs that didn’t run as expected would help us to better identify where the cause of the issue may lie.

thanks for the reply, i will check the recent trigger data and compare the successful and failed runs more carefully. I will also share the screenshot of the ZAP setup and task history details so it is easier to understand what might be causing the issue.

Sounds good to me ​@Adilbabu. We’ll keep an eye out for those screenshots! 🙂

Hi Adilbabu,

For a random failure where the trigger is detected but a later action does not complete, I would compare one successful run and one failed run side by side before rebuilding the Zap.

The first checklist I would use:

1. trigger `Data Out` shape on the good run versus the failed run,
2. each filter/path decision after the trigger,
3. action `Data In` on the step that stops,
4. whether the action step shows skipped, held, throttled, or no-op behavior,
5. any recently changed trigger fields or empty values that used to be populated.

No credentials are needed for a first diagnosis. A redacted run-history comparison for one good run and one bad run is usually enough to identify whether this is changed input shape, a filter/path stop, or an app action that is failing without surfacing a clear error.