Workflow running 4 hours late

[andrewstrealtor]

Your Task History ID

IjU3NmMwNTZlMDYzMzA0MzQ1MjY0NTUzMTUxMzI1MTY2NTQzNiI_3D_pc

I am trying to trace some issue and I'm seeing that my workflows are not triggering when the webhook is sent. This one example ran 4 hour late today. Why is this happening?

In the attached images, I am showing you that the time zone is set correctly both in Pabbly and in my system sending the webhooks. The webhook was sent at 2:10pm but wasn't logged as received until 6:10pm. I have no idea when it actually ran and whether or not the issue is not whether it ran on time or not or if the time zone setting isn't applying and all the times are wrong.

Also in the photos I'm showing the time code of when the webhook was sent and when the workflow initial trigger step started after receiving the webhook. My system would not have sent the webhook again which means although it was sent at 2:10pm, your system is saying it didn't start until 4 horus later.

I'm also trying to find another workflow in the history since I'm not seeing the result of it having run even though I sent the webhook at 4:10pm and this is where I found the other issue of workflows now not running or running late. What is going on and why did this happen? Is this going to continue to happen?

 

[Supreme]

Hey @andrewstrealtor

Upon closer examination of the task history ID, you'll notice that there is a difference in the time when the trigger was received and when the workflow was executed. This difference is due to the display time in the task history reflecting the time when the workflow processed the task until completion.

The webhook only captures the response data which was sent by the application itself and it is something that we cannot manipulate. If your data is not arriving or coming late so there is a good chance that it is not being sent/delayed to Pabbly Connect's webhook URL In cases like these, you will have to contact the support team of API for which you to see why your data is not coming.

To double-check, you can also confirm it through a webbooks testing site by the name of webhook.site.

You can copy the webhook URL provided by Webhook.site inside API and do the test event inside Landingi to see if the webhook is being captured or not inside Webhook.site. This will double-confirm the issue.

Here is a sample video that you can follow to track the webhook issue:

You can check out the following video for your concern -