Full history of a workflow not showing

Status: Closed · Asked by Dan Cook on · 0 views

Dan Cook — Question ·
The latest run is not showing any history othet than the trigger. 8 api calls were not performed and I was looking to investigate why and none of the history is showing.

image.png
Pabbly Support — Reply ·

Hello Dan,

Thank you for reaching out to us and for sharing the workflow URL and the relevant details.

The issue you’re experiencing can occur when the complete task history for a particular workflow run is unable to finish within the time limit configured on our backend, which is approximately 20 minutes. It appears that this particular run may have taken longer than the specified timeframe, which could be why the subsequent steps are not visible in the Task History.

To confirm whether the subsequent actions were actually executed, could you please check the respective applications for which you have configured the actions and verify whether the corresponding records/entries have been logged there?

Once you confirm this, we’ll escalate the issue to our technical team for further investigation and review.

We appreciate your cooperation and look forward to your confirmation.

Thanks and Regards,
Preeti Paryani
Customer Success Associate,
Pabbly.com
Dan Cook — Reply ·

Hi Preeti,

Hope you're doing well and had a nice weekend.

The run never fully completed. There were 8 API calls missed (never done) but from my own digging, the missing 8 would have been next in the list. So it was not like 8 random API calls were missed throughout, it was more like it got to a certain point and just stopped. So you are likely correct, the run was not able to finish within the 20 minutes. For such a small workflow it does a fair amount.

Pabbly Support — Reply ·

Hello Dan,

We have escalated this case to our technical team for further investigation. We have shared the workflow details and execution information with them so they can review the cause behind the incomplete execution.

We will update you once we receive further findings from the team.

Thank you for your patience and cooperation.

Thanks & Regards,
Naman Bansod
Customer Support Specialist
🌐 Pabbly.com
👉 Rate your support
Pabbly Support — Reply ·

Hello Dan,

Thanks for your patience.

The team has identified that the workflow is quite large, and the execution may end before the complete Task History is saved.

As a temporary workaround, please add a 1-minute Delay step as the first step inside the Loop, as shown in the workflow.

image.png

Please make sure the Delay is inside the Loop, not after it. This will allow the system to save the execution progress during each loop iteration and help prevent the Task History from being lost.

This is a temporary workaround, and a permanent fix is already planned.

Please try this and let us know whether the complete execution is now reflected in the Task History.

Thanks & Regards,
Naman Bansod
Customer Support Specialist
🌐 Pabbly.com
👉 Rate your support

Back to all forum threads · Log in to reply