Knowledge Drop
Last tested: June 2021
No. Any query run in the UI (or API) will be subject to the proxy timeout rules, and it is not possible to increase that timeout past 60 minutes.
If you're trying to build PDTs that take longer than an hour then you have a few workaround options.
Workaround 1
Use the --if dev-- parameter or some other where clause to make the PDT take less than an hour.
Workaround 2
Push the code to production and let the regenerator handle the build. (Make sure it has a sql_trigger_value so that the regenerator does attempt to build it.) That will circumvent the proxy. That way, you can have the PDT take as long as you need.
Workaround 3
If using the API, you can leverage async query tasks to get around this! You can run create_query() to make a query, pass that returned query id into create_query_task(query_id), then check on the query using query_task(task_id) to see when it is finished, then finally use query_task_results(task_id) to get the results of the query!
⚠️ Only scheduled/trigger jobs (built by the regenerator) circumvent the proxy timeout in production, if you rebuild a PDT from the front end manually, the timeout still applies.
LinkedIn
Twitter