I have an example that is showing this issue that seems to be occurring on a lot of calls. (See Attached)
The call in this example started at Jan 23, 1:26pm which the call start workflow picks up and starts right away, which works flawlessly.
On the contact view, you can see that the call started at the same time and the duration was only 1:37 yet the Call End Workflow did not initiate until Jan 23, 1:33pm.
The long and short of this is that this end call trigger is not firing fast enough to make this a reliable way to send this webhooks or other time sensitive tasks.
Is this a bug? Are there any other suggestion or ways I could trigger this faster? This needs to initate immediatly after the call.
I’m tagging some experts from our community who can lend a hand to figure this out. Hey @evaldas@SteveHTM and @RubenBurdin do you have some advice or to help us out here please?
@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.
@SteveHTM Thanks for the reply! I understand the timing can vary since there are a hundred other things that are being queued and moved at any given moment. I find it odd that the Call Start Trigger seems it initiate immediatly though, in my testing it will always fire the second a call start is triggered.
I am going through support right now on this issue just to be sure that what you explained is the case for this particular problem. Are there any other solutions that could help expedite a webhook off of a call or action?
So talking with support there is a intentional 5 minute delay in any of the call complete workflow triggers so it can collect the manual data like Call Outcomes and so on.
As of right now there is no way to get around this delay besides triggering a workflow off of maunal changes to a property on the contact.
