Data was forwarded in webhook successfully, but receiving workflow never executed it

[JeffreyYu]

Your Task History ID

IjU3NjUwNTZkMDYzMzA0M2Q1MjZiNTUzMTUxMzA1MTYzNTQzMjBmMzYi_pc

Hi Pabbly!

After investigating a customer complaint, I investigated and found that we never received the following request in our Airtable database. It looks like it's because our workflow was never triggered, despite the data being forwarded to it successfully.

This is for the Async Request Received (Preferred) workflow, with task data Order ID: F49E13T1. As you can see, it was forwarded successfully:

However, there are no results showing that the workflow executed after being sent this webhook.

The really bizarre thing is that the other 19 requests with this workflow combination (Async Request Received [Preferred] -> [Without PS Ratio] Process New Async Request) worked just fine. I'm not sure why it didn't throw an error or execute it?

 

[Preeti Paryani]

Hello @JeffreyYu

To check the issue we have re-executed the workflow history of the Async Request Received (Preferred) workflow, with task data Order ID: F49E13T1 and it triggered the [Without PS Ratio] Process New Async Request. Please refer to the screenshot for more info.

Can you please check and let us know if there are more such events where the data forwarder shows as success and the preceding workflow didn't get triggered?

 

[JeffreyYu]

Yes, it was triggered! Did you manage to figure out why the data forwarder did not trigger the secondary workflow?

 

[Preeti Paryani]

Hello @JeffreyYu

Unfortunately, we were unable to figure out the exact reason behind the issue, but we have recently made some updates that may have caused it.

If you face the same issue further please let us know.