charaf_ed | 2019-09-25 11:51:09 UTC | #1
Hello,
Would it be possible to extend the Timeout when executing a PureCloud Data Action from a script ? (I noticed that when calling the Data Actions from the IVR, we can change the Timeout)
Regards,
Jason_Mathison | 2019-09-25 12:18:11 UTC | #2
Short answer is no. Scripts run Data Actions via Public API which imposes a 20 second timeout.
This particular test execution hit the 20 second public API timeout. Data Actions run via the IVR do not go through Public API, so they do not have the same timeout limitations.
FYI, the underlying query did succeed, but it took 28.6 seconds.
--Jason
charaf_ed | 2019-09-25 12:40:24 UTC | #3
Thank you for your answer @Jason_Mathison
How do you know that query succeeded ? knowing that all the output that I got were empty !
Regards,
Jason_Mathison | 2019-09-25 13:22:21 UTC | #4
I know based on looking up the contextId you provided in our internal logging system.
charaf_ed | 2019-09-25 13:24:26 UTC | #5
Ah okay
Does the CRM sent us information ? because in PureCloud side We have empty fields !!
Jason_Mathison | 2019-09-25 13:39:04 UTC | #6
I would assume that the CRM sent back whatever you would expect from that query, however we intentionally do not trace out the query or the results. Once Public API times out your request the results are lost.
We have seen examples of "cold queries" (the first query run in more than an hour) taking an exceptionally long time with the CRM you are using. If you wait a minute and run a couple more tests of the query does it still time out? If it is consistently timing out then you probably need to look into optimizing your query.
charaf_ed | 2019-09-25 15:29:51 UTC | #7
Now it's working after the first long query.
system | 2019-10-25 15:33:05 UTC | #8
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 6103