I am observing the advanced tab query timeout for javascript queries to be hardcoded and uneditable with 10 seconds as the value.
Is this correct? Is this is not modifiable? If so why?
Hi @Tolga_Erdogus,
It's actually not supported to timeout Javascript queries, that's why the option is disabled. If you write an infinite loop in a Javascript query, it will run forever.
However, this is a confusing experience, and the field should be hidden entirely.
I'll go ahead and log that issue.
Thanks!
Ok - so then if I want a long running javascript then I should add it to a workflow and pass UI based parameters to the trigger of the workflow that runs the javascript? Would this then allow me to have the max (120 seconds) timeout on the javascript code inside the workflow?
Your in-app javascript can run forever, there is no timeout (contrary to the disabled 10000ms value you see in the UI).
However, if you're running synchronous code, then it will occupy the main thread of the runtime and lock up your application.
If you need to do long running synchronous code, a workflow is a great solution.