Wdata Timeout
Hello - I have noticed that occasionally in our environment, Wdata queries will timeout. It looks to be a 10-minute timeout process, and when it happens, it occurs for all chains / scripts / etc. that are running Wdata at that time. Is this a platform-wide load timeout, or is there something specific to our environment that could be causing this?
The issue is not too bothersome, as the vast majority of the time the chain / script / etc. succeeds on the next run. Just looking for some clarity so I can provide an explanation to our team for why this happens ever so often.
-
Hey Joe Rufolo — happy to provide some clarity on this.The 10-minute timeout is a platform-wide limit enforced by the Workiva API — it is not specific to your environment. The Wdata API limits the length of any request to 10 minutes. This applies across chains, scripts, and any other mechanism running Wdata queries.The 10-minute timeout cannot be extended — it is a hard platform limit.Hope this is a little bit helpful for you!More details can be found here on our Support Site: Wdata Feature and API Limits0
Hi Brooke,
Thank you for the quick response! In addition, I was curious why this happens / if Wdata capacity is platform wide. These queries usually only take 5-20 seconds to run, so just curious if you have any insight into this. Thanks!
0댓글을 남기려면 로그인하세요.
댓글
댓글 2개