Hi @eliav2 , yes, I should have updated this post a while ago but forgot to do so. Essentially, what I discovered was that the javascript 'require' call (which I mention above in the post) was timing out when several Splunk queries were being access simultaneously. This in particular, is not a Splunk limitation, but a timing limitation in that function. I was able to temporarily do away with this timeout by changing the parameters being passed to 'require'. Specifically, I ended up with this call: // Configure the web site's base URL require.config({ baseUrl: "static/", waitSeconds: 0 }); Note the 'waitSeconds' value above., which would normally not be included. Ultimately though, I ended up understanding the reality that Splunk's performance is the real culprit when writing this type of applications, and I did what I could to 'optimize' the queries that I was running simultaneously on one web page (even sequencing some of them to avoid some of the concurrency). This continues to be an issue for us and we haven't really found a good solution to the problem in general. If you find out some other way please post it here. Good luck with your optimization!
... View more