Hello
I have noticed than when an Architect Task has to execute several Data Table Lookup Actions (for example, within a loop), the Task takes longer to start, like half a second for each lookup.
I was wondering if there is a way to make this process faster besides using an API call, because that would require to create a Role, an OAuth, an Integration and a Data Action, just for this purpose.
Thank you
Do you have an unnecessary actions in the task?
You can add audio before the loop if you want to warn the caller about the long pause.
No, I don't have unnecessary actions in the task. It also happens that the delay does not occur just before the loop, but at the beggining of the task. So, if the task is:
Play Audio "Hello" -> Datatable lookup x6 -> Play Audio "Goodbye"
What happens is:
3 seconds delay -> "Hello" -> "Goodbye".
Also in many cases we want to do the lookup at the beggining of the flow, and it is not pleasant for the client to have to wait 3 seconds when the call has just started.
This is not obvious because most actions execute so quickly, but audio is not played immediately. It's queued up until it gets to an action that triggers all the queued audio to play now. To force audio to play immediately, add a Collect Input action after the audio action, or in your case as the 1st action of the task. Set all the timeouts to the smallest possible value & don't use a verification method.
Thank you Melissa
I understand then that there is no way to speed up the lookup besides using an API call, right?
Not really. You could open a ticket with support to have them look at the break down of where the time is spent.
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.