# Call End Workflow Trigger Delay Bug **URL:** \ **Category:** CMS Development\ **Tags:** local-development\ **Created:** [January 23, 2026, 8:59pm UTC](https://community.hubspot.com/t/call-end-workflow-trigger-delay-bug/145334 "2026-01-23T20:59:33Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![SteveHTM](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/stevehtm/32/22074_2.png) [@SteveHTM](https://community.hubspot.com/u/SteveHTM)\ **Post date:** [January 23, 2026, 10:18pm UTC](https://community.hubspot.com/t/call-end-workflow-trigger-delay-bug/145334/5 "2026-01-23T22:18:42Z")
@BButz - When you think about it, there is a pretty large overhead in the initialization and execution of a workflow. As I understand it, each thread like this is effectively a AWS Lambda environment (or something real similar), and competes with other threads of execution for resources. Nothing in HubSpot is really guaranteed as real-time, so you have to expect a spectrum of delay times for all functions. You can potentially optimize things to be as lightweight as possible, and the action is reliablly executed, but I always assume that timing between functions is a bit indeterminate. Hope this is helpful. Steve --- _[View the full topic](https://community.hubspot.com/t/call-end-workflow-trigger-delay-bug/145334)._