Skip to content

The easy-to-use open source Business Intelligence and Embedded Analytics tool that lets everyone work with data :bar_chart:

docs - notes on timeouts (#70468)

Jeff Bruemmer5cd8e165fa88
diff --git a/src/metabase/driver/settings.clj b/src/metabase/driver/settings.clj
index 6d2540550e4..7ff38565a69 100644
--- a/src/metabase/driver/settings.clj
+++ b/src/metabase/driver/settings.clj
@@ -95,9 +95,12 @@
:default (if config/is-prod?
20
3)
- :doc "Timeout in minutes for databases query execution, both Metabase application database and data connections.
- If you have long-running queries, you might consider increasing this value.
- Adjusting the timeout does not impact Metabase’s frontend.
+ :doc "Timeout in minutes for the database's query execution, both for the Metabase application database and any data connections.
+ If you have long-running queries, you might consider increasing this value. Adjusting the timeout does not impact Metabase’s frontend.
+
+ This setting also applies to individual queries executed within transforms, so make sure the duration is long enough
+ that it doesn't timeout any long-running queries in your transforms.
+
Please be aware that other services (like Nginx) may still drop long-running queries.")
;; This is normally set via the env var `MB_JDBC_NETWORK_TIMEOUT_MS`
diff --git a/src/metabase/transforms/settings.clj b/src/metabase/transforms/settings.clj
index 201f46e240b..ef4e2a8ba75 100644
--- a/src/metabase/transforms/settings.clj
+++ b/src/metabase/transforms/settings.clj
@@ -10,8 +10,9 @@
:type :integer
:visibility :internal
:default (* 4 60)
+ :doc "Each query executed by a transform is also subject to the MB_DB_QUERY_TIMEOUT_MINUTES timeout,
+ so make sure that value isn't lower, or it will timeout your transform."
:feature :transforms-basic
- :doc false
:export? false
:encryption :no
:audit :getter)