diff --git a/content/influxdb3/cloud-dedicated/query-data/execute-queries/client-libraries/python.md b/content/influxdb3/cloud-dedicated/query-data/execute-queries/client-libraries/python.md
index ad173145ee..0ae8e82cbd 100644
--- a/content/influxdb3/cloud-dedicated/query-data/execute-queries/client-libraries/python.md
+++ b/content/influxdb3/cloud-dedicated/query-data/execute-queries/client-libraries/python.md
@@ -26,6 +26,7 @@ related:
     - /influxdb3/cloud-dedicated/reference/influxql/
     - /influxdb3/cloud-dedicated/reference/sql/
     - /influxdb3/cloud-dedicated/query-data/execute-queries/troubleshoot/
+    - /influxdb3/cloud-dedicated/query-data/troubleshoot-and-optimize/query-timeout-best-practices/
 
 list_code_example: |
     ```py
@@ -240,7 +241,8 @@ from influxdb_client_3 import InfluxDBClient3
 client = InfluxDBClient3(
     host='{{< influxdb/host >}}',
     token='DATABASE_TOKEN',
-    database='DATABASE_NAME'
+    database='DATABASE_NAME',
+    timeout=60  # Set default timeout to 60 seconds
 )
 ```
 {{% /code-placeholders %}}
@@ -275,6 +277,7 @@ client = InfluxDBClient3(
 host="{{< influxdb/host >}}",
 token='DATABASE_TOKEN',
 database='DATABASE_NAME',
+timeout=60,  # Set default timeout to 60 seconds
 flight_client_options=flight_client_options(
 tls_root_certs=cert))
 ...
@@ -332,7 +335,8 @@ client = InfluxDBClient3(
 # Execute the query and return an Arrow table
 table = client.query(
     query="SELECT * FROM home",
-    language="sql"
+    language="sql",
+    timeout=30  # Override default timeout for simple queries (30 seconds)
 )
 
 print("\n#### View Schema information\n")
@@ -377,7 +381,8 @@ client = InfluxDBClient3(
 # Execute the query and return an Arrow table
 table = client.query(
     query="SELECT * FROM home",
-    language="influxql"
+    language="influxql",
+    timeout=30  # Override default timeout for simple queries (30 seconds)
 )
 
 print("\n#### View Schema information\n")
diff --git a/content/influxdb3/cloud-dedicated/query-data/execute-queries/influxctl-cli.md b/content/influxdb3/cloud-dedicated/query-data/execute-queries/influxctl-cli.md
index 92d8864743..446f3d73ef 100644
--- a/content/influxdb3/cloud-dedicated/query-data/execute-queries/influxctl-cli.md
+++ b/content/influxdb3/cloud-dedicated/query-data/execute-queries/influxctl-cli.md
@@ -13,6 +13,7 @@ influxdb3/cloud-dedicated/tags: [query, sql, influxql, influxctl, CLI]
 related:
   - /influxdb3/cloud-dedicated/reference/cli/influxctl/query/
   - /influxdb3/cloud-dedicated/get-started/query/#execute-an-sql-query, Get started querying data
+  - /influxdb3/cloud-dedicated/query-data/troubleshoot-and-optimize/query-timeout-best-practices/, Query timeout best practices
   - /influxdb3/cloud-dedicated/reference/sql/
   - /influxdb3/cloud-dedicated/reference/influxql/
 list_code_example: |
@@ -142,6 +143,34 @@ Replace the following:
 - {{% code-placeholder-key %}}`DATABASE_NAME`{{% /code-placeholder-key %}}:
   Name of the database to query
 
+## Query timeouts
+
+The [`influxctl --timeout` global flag](/influxdb3/cloud-dedicated/reference/cli/influxctl/) sets the maximum duration for API calls, including query requests.
+If a query takes longer than the specified timeout, the operation will be canceled.
+
+### Timeout examples
+
+Use different timeout values based on your query type:
+
+{{% code-placeholders "DATABASE_(TOKEN|NAME)" %}}
+```sh
+# Shorter timeout for testing dashboard queries (10 seconds)
+influxctl query \
+  --timeout 10s \
+  --token DATABASE_TOKEN \
+  --database DATABASE_NAME \
+  "SELECT AVG(temperature) FROM sensors WHERE time >= now() - INTERVAL '1 day'"
+
+# Longer timeout for analytical queries (5 minutes)
+influxctl query \
+  --timeout 5m \
+  --token DATABASE_TOKEN \
+  --database DATABASE_NAME \
+  "SELECT room, AVG(temperature) FROM sensors WHERE time >= now() - INTERVAL '30 days' GROUP BY room"
+```
+{{% /code-placeholders %}}
+
+For guidance on selecting appropriate timeout values, see [Query timeout best practices](/influxdb3/cloud-dedicated/query-data/troubleshoot-and-optimize/query-timeout-best-practices/).
 
 ## Output format
 
@@ -243,7 +272,7 @@ influxctl query \
 {{% /influxdb/custom-timestamps %}}
 
 {{< expand-wrapper >}}
-{{% expand "View example results with unix nanosecond timestamps" %}}
+{{% expand "View example results with Unix nanosecond timestamps" %}}
 {{% influxdb/custom-timestamps %}}
 ```
 +-------+--------+---------+------+---------------------+
diff --git a/content/influxdb3/cloud-dedicated/query-data/troubleshoot-and-optimize/query-timeout-best-practices.md b/content/influxdb3/cloud-dedicated/query-data/troubleshoot-and-optimize/query-timeout-best-practices.md
new file mode 100644
index 0000000000..fb4a1c8752
--- /dev/null
+++ b/content/influxdb3/cloud-dedicated/query-data/troubleshoot-and-optimize/query-timeout-best-practices.md
@@ -0,0 +1,17 @@
+---
+title: Query timeout best practices
+description: Learn how to set appropriate query timeouts to balance performance and resource protection.
+menu:
+  influxdb3_cloud_dedicated:
+    name: Query timeout best practices
+    parent: Troubleshoot and optimize queries
+weight: 205
+related:
+  - /influxdb3/cloud-dedicated/reference/client-libraries/v3/
+  - /influxdb3/cloud-dedicated/query-data/execute-queries/influxctl-cli/
+source: shared/influxdb3-query-guides/query-timeout-best-practices.md
+---
+
+<!--
+//SOURCE - content/shared/influxdb3-query-guides/query-timeout-best-practices.md
+>
\ No newline at end of file
diff --git a/content/influxdb3/cloud-dedicated/query-data/troubleshoot-and-optimize/troubleshoot.md b/content/influxdb3/cloud-dedicated/query-data/troubleshoot-and-optimize/troubleshoot.md
index 70ba8dd155..bd89d15e78 100644
--- a/content/influxdb3/cloud-dedicated/query-data/troubleshoot-and-optimize/troubleshoot.md
+++ b/content/influxdb3/cloud-dedicated/query-data/troubleshoot-and-optimize/troubleshoot.md
@@ -12,6 +12,7 @@ related:
   - /influxdb3/cloud-dedicated/query-data/sql/
   - /influxdb3/cloud-dedicated/query-data/influxql/
   - /influxdb3/cloud-dedicated/reference/client-libraries/v3/
+  - /influxdb3/cloud-dedicated/query-data/troubleshoot-and-optimize/query-timeout-best-practices/
 aliases:
   - /influxdb3/cloud-dedicated/query-data/execute-queries/troubleshoot/
   - /influxdb3/cloud-dedicated/query-data/troubleshoot-and-optimize/trace/
@@ -30,7 +31,9 @@ If a query doesn't return any data, it might be due to the following:
 
 - Your data falls outside the time range (or other conditions) in the query--for example, the InfluxQL `SHOW TAG VALUES` command uses a default time range of 1 day.
 - The query (InfluxDB server) timed out.
-- The query client timed out.
+- The query client timed out. 
+  See [Query timeout best practices](/influxdb3/cloud-dedicated/query-data/troubleshoot-and-optimize/query-timeout-best-practices/) 
+  for guidance on setting appropriate timeouts.
 - The query return type is not supported by the client library.
   For example, array or list types may not be supported.
   In this case, use `array_to_string()` to convert the array value to a string--for example:
diff --git a/content/influxdb3/cloud-serverless/query-data/execute-queries/client-libraries/python.md b/content/influxdb3/cloud-serverless/query-data/execute-queries/client-libraries/python.md
index cd2545135a..da203588de 100644
--- a/content/influxdb3/cloud-serverless/query-data/execute-queries/client-libraries/python.md
+++ b/content/influxdb3/cloud-serverless/query-data/execute-queries/client-libraries/python.md
@@ -27,6 +27,7 @@ related:
     - /influxdb3/cloud-serverless/reference/influxql/
     - /influxdb3/cloud-serverless/reference/sql/
     - /influxdb3/cloud-serverless/query-data/execute-queries/troubleshoot/
+    - /influxdb3/cloud-serverless/query-data/troubleshoot-and-optimize/query-timeout-best-practices/
 
 list_code_example: |
     ```py
@@ -241,7 +242,8 @@ from influxdb_client_3 import InfluxDBClient3
 client = InfluxDBClient3(
     host='{{< influxdb/host >}}',
     token='API_TOKEN',
-    database='BUCKET_NAME'
+    database='BUCKET_NAME',
+    timeout=30  # Set default timeout to 30 seconds for serverless
 )
 ```
 {{% /code-placeholders %}}
@@ -332,7 +334,8 @@ client = InfluxDBClient3(
 # Execute the query and return an Arrow table
 table = client.query(
     query="SELECT * FROM home",
-    language="sql"
+    language="sql",
+    timeout=10  # Override default timeout for simple queries (10 seconds)
 )
 
 print("\n#### View Schema information\n")
@@ -377,7 +380,8 @@ client = InfluxDBClient3(
 # Execute the query and return an Arrow table
 table = client.query(
     query="SELECT * FROM home",
-    language="influxql"
+    language="influxql",
+    timeout=10  # Override default timeout for simple queries (10 seconds)
 )
 
 print("\n#### View Schema information\n")
diff --git a/content/influxdb3/cloud-serverless/query-data/troubleshoot-and-optimize/query-timeout-best-practices.md b/content/influxdb3/cloud-serverless/query-data/troubleshoot-and-optimize/query-timeout-best-practices.md
new file mode 100644
index 0000000000..e337f6664c
--- /dev/null
+++ b/content/influxdb3/cloud-serverless/query-data/troubleshoot-and-optimize/query-timeout-best-practices.md
@@ -0,0 +1,17 @@
+---
+title: Query timeout best practices
+description: Learn how to set appropriate query timeouts to balance performance and resource protection.
+menu:
+  influxdb3_cloud_serverless:
+    name: Query timeout best practices
+    parent: Troubleshoot and optimize queries
+    identifier: query-timeout-best-practices
+weight: 201
+related:
+  - /influxdb3/cloud-serverless/reference/client-libraries/v3/
+source: shared/influxdb3-query-guides/query-timeout-best-practices.md
+---
+
+<!--
+//SOURCE - content/shared/influxdb3-query-guides/query-timeout-best-practices.md
+>
\ No newline at end of file
diff --git a/content/influxdb3/cloud-serverless/query-data/troubleshoot-and-optimize/troubleshoot.md b/content/influxdb3/cloud-serverless/query-data/troubleshoot-and-optimize/troubleshoot.md
index 5c919861aa..31edbebb91 100644
--- a/content/influxdb3/cloud-serverless/query-data/troubleshoot-and-optimize/troubleshoot.md
+++ b/content/influxdb3/cloud-serverless/query-data/troubleshoot-and-optimize/troubleshoot.md
@@ -12,6 +12,7 @@ related:
   - /influxdb3/cloud-serverless/query-data/sql/
   - /influxdb3/cloud-serverless/query-data/influxql/
   - /influxdb3/cloud-serverless/reference/client-libraries/v3/
+  - /influxdb3/cloud-serverless/query-data/troubleshoot-and-optimize/query-timeout-best-practices/
 aliases:
   - /influxdb3/cloud-serverless/query-data/execute-queries/troubleshoot/
 ---
@@ -29,7 +30,9 @@ If a query doesn't return any data, it might be due to the following:
 
 - Your data falls outside the time range (or other conditions) in the query--for example, the InfluxQL `SHOW TAG VALUES` command uses a default time range of 1 day.
 - The query (InfluxDB server) timed out.
-- The query client timed out.
+- The query client timed out. 
+  See [Query timeout best practices](/influxdb3/cloud-serverless/query-data/troubleshoot-and-optimize/query-timeout-best-practices/) 
+  for guidance on setting appropriate timeouts.
 - The query return type is not supported by the client library.
   For example, array or list types may not be supported.
   In this case, use `array_to_string()` to convert the array value to a string--for example:
diff --git a/content/influxdb3/clustered/query-data/execute-queries/client-libraries/python.md b/content/influxdb3/clustered/query-data/execute-queries/client-libraries/python.md
index 444e109d22..c64e2f6817 100644
--- a/content/influxdb3/clustered/query-data/execute-queries/client-libraries/python.md
+++ b/content/influxdb3/clustered/query-data/execute-queries/client-libraries/python.md
@@ -20,6 +20,7 @@ related:
     - /influxdb3/clustered/query-data/sql/
     - /influxdb3/clustered/reference/influxql/
     - /influxdb3/clustered/reference/sql/
+    - /influxdb3/clustered/query-data/troubleshoot-and-optimize/query-timeout-best-practices/
 
 list_code_example: |
     ```py
@@ -234,7 +235,8 @@ from influxdb_client_3 import InfluxDBClient3
 client = InfluxDBClient3(
     host='{{< influxdb/host >}}',
     token='DATABASE_TOKEN',
-    database='DATABASE_NAME'
+    database='DATABASE_NAME',
+    timeout=60  # Set default timeout to 60 seconds
 )
 ```
 {{% /code-placeholders %}}
@@ -325,7 +327,8 @@ client = InfluxDBClient3(
 # Execute the query and return an Arrow table
 table = client.query(
     query="SELECT * FROM home",
-    language="sql"
+    language="sql",
+    timeout=30  # Override default timeout for simple queries (30 seconds)
 )
 
 print("\n#### View Schema information\n")
@@ -370,7 +373,8 @@ client = InfluxDBClient3(
 # Execute the query and return an Arrow table
 table = client.query(
     query="SELECT * FROM home",
-    language="influxql"
+    language="influxql",
+    timeout=30  # Override default timeout for simple queries (30 seconds)
 )
 
 print("\n#### View Schema information\n")
diff --git a/content/influxdb3/clustered/query-data/execute-queries/influxctl-cli.md b/content/influxdb3/clustered/query-data/execute-queries/influxctl-cli.md
index d218f03a18..f3f19e2aa6 100644
--- a/content/influxdb3/clustered/query-data/execute-queries/influxctl-cli.md
+++ b/content/influxdb3/clustered/query-data/execute-queries/influxctl-cli.md
@@ -12,6 +12,7 @@ influxdb3/clustered/tags: [query, sql, influxql, influxctl, CLI]
 related:
   - /influxdb3/clustered/reference/cli/influxctl/query/
   - /influxdb3/clustered/get-started/query/#execute-an-sql-query, Get started querying data
+  - /influxdb3/clustered/query-data/troubleshoot-and-optimize/query-timeout-best-practices/, Query timeout best practices
   - /influxdb3/clustered/reference/sql/
   - /influxdb3/clustered/reference/influxql/
 list_code_example: |
@@ -141,6 +142,35 @@ Replace the following:
 - {{% code-placeholder-key %}}`DATABASE_NAME`{{% /code-placeholder-key %}}:
   Name of the database to query
 
+## Query timeouts
+
+The [`influxctl --timeout` global flag](/influxdb3/clustered/reference/cli/influxctl/) sets the maximum duration for API calls, including query requests.
+If a query takes longer than the specified timeout, the operation will be canceled.
+
+### Timeout examples
+
+Use different timeout values based on your query type:
+
+{{% code-placeholders "DATABASE_(TOKEN|NAME)" %}}
+```sh
+# Shorter timeout for testing dashboard queries (10 seconds)
+influxctl query \
+  --timeout 10s \
+  --token DATABASE_TOKEN \
+  --database DATABASE_NAME \
+  "SELECT * FROM sensors WHERE time >= now() - INTERVAL '1 hour' LIMIT 100"
+
+# Longer timeout for analytical queries (5 minutes)
+influxctl query \
+  --timeout 300s \
+  --token DATABASE_TOKEN \
+  --database DATABASE_NAME \
+  "SELECT room, AVG(temperature) FROM sensors WHERE time >= now() - INTERVAL '30 days' GROUP BY room"
+```
+{{% /code-placeholders %}}
+
+For guidance on selecting appropriate timeout values, see [Query timeout best practices](/influxdb3/clustered/query-data/troubleshoot-and-optimize/query-timeout-best-practices/).
+
 ## Output format
 
 The `influxctl query` command supports the following output formats:
@@ -241,7 +271,7 @@ influxctl query \
 {{% /influxdb/custom-timestamps %}}
 
 {{< expand-wrapper >}}
-{{% expand "View example results with unix nanosecond timestamps" %}}
+{{% expand "View example results with Unix nanosecond timestamps" %}}
 {{% influxdb/custom-timestamps %}}
 ```
 +-------+--------+---------+------+---------------------+
diff --git a/content/influxdb3/clustered/query-data/troubleshoot-and-optimize/query-timeout-best-practices.md b/content/influxdb3/clustered/query-data/troubleshoot-and-optimize/query-timeout-best-practices.md
new file mode 100644
index 0000000000..532f2f9767
--- /dev/null
+++ b/content/influxdb3/clustered/query-data/troubleshoot-and-optimize/query-timeout-best-practices.md
@@ -0,0 +1,18 @@
+---
+title: Query timeout best practices
+description: Learn how to set appropriate query timeouts to balance performance and resource protection.
+menu:
+  influxdb3_clustered:
+    name: Query timeout best practices
+    parent: Troubleshoot and optimize queries
+    identifier: query-timeout-best-practices
+weight: 201
+related:
+  - /influxdb3/clustered/reference/client-libraries/v3/
+  - /influxdb3/clustered/query-data/execute-queries/influxctl-cli/
+source: shared/influxdb3-query-guides/query-timeout-best-practices.md
+---
+
+<!--
+//SOURCE - content/shared/influxdb3-query-guides/query-timeout-best-practices.md
+>
\ No newline at end of file
diff --git a/content/influxdb3/clustered/query-data/troubleshoot-and-optimize/troubleshoot.md b/content/influxdb3/clustered/query-data/troubleshoot-and-optimize/troubleshoot.md
index 2ba49d45b3..c3a97fad3a 100644
--- a/content/influxdb3/clustered/query-data/troubleshoot-and-optimize/troubleshoot.md
+++ b/content/influxdb3/clustered/query-data/troubleshoot-and-optimize/troubleshoot.md
@@ -12,6 +12,7 @@ related:
   - /influxdb3/clustered/query-data/sql/
   - /influxdb3/clustered/query-data/influxql/
   - /influxdb3/clustered/reference/client-libraries/v3/
+  - /influxdb3/clustered/query-data/troubleshoot-and-optimize/query-timeout-best-practices/
 aliases:
   - /influxdb3/clustered/query-data/execute-queries/troubleshoot/
 ---
@@ -29,7 +30,9 @@ If a query doesn't return any data, it might be due to the following:
 
 - Your data falls outside the time range (or other conditions) in the query--for example, the InfluxQL `SHOW TAG VALUES` command uses a default time range of 1 day.
 - The query (InfluxDB server) timed out.
-- The query client timed out.
+- The query client timed out. 
+  See [Query timeout best practices](/influxdb3/clustered/query-data/troubleshoot-and-optimize/query-timeout-best-practices/) 
+  for guidance on setting appropriate timeouts.
 - The query return type is not supported by the client library.
   For example, array or list types may not be supported.
   In this case, use `array_to_string()` to convert the array value to a string--for example:
diff --git a/content/shared/influxdb3-query-guides/query-timeout-best-practices.md b/content/shared/influxdb3-query-guides/query-timeout-best-practices.md
new file mode 100644
index 0000000000..c101123c70
--- /dev/null
+++ b/content/shared/influxdb3-query-guides/query-timeout-best-practices.md
@@ -0,0 +1,301 @@
+Learn how to set appropriate query timeouts for InfluxDB 3 to balance performance and resource protection.
+
+Query timeouts prevent resource monopolization while allowing legitimate queries to complete successfully.
+The key is finding the "goldilocks zone"—timeouts that are not too short (causing legitimate queries to fail) and not too long (allowing runaway queries to monopolize resources).
+
+- [Understanding query timeouts](#understanding-query-timeouts)
+- [How query routing affects timeout strategy](#how-query-routing-affects-timeout-strategy)
+- [Timeout configuration best practices](#timeout-configuration-best-practices)
+- [InfluxDB 3 client library examples](#influxdb-3-client-library-examples)
+- [Monitoring and troubleshooting](#monitoring-and-troubleshooting)
+
+## Understanding query timeouts
+
+Query timeouts define the maximum duration a query can run before being canceled.
+In {{% product-name %}}, timeouts serve multiple purposes:
+
+- **Resource protection**: Prevent runaway queries from monopolizing system resources
+- **Performance optimization**: Ensure responsive system behavior for time-sensitive operations
+- **Cost control**: Limit compute resource consumption
+- **User experience**: Provide predictable response times for applications and dashboards
+
+Query execution includes network latency, query planning, data retrieval, processing, and result serialization.
+
+### The "goldilocks zone" for query timeouts
+
+Optimal timeouts are:
+- **Long enough**: To accommodate normal query execution under typical load
+- **Short enough**: To prevent resource monopolization and provide reasonable feedback
+- **Adaptive**: Adjusted based on query type, system load, and historical performance
+
+## How query routing affects timeout strategy
+
+InfluxDB 3 uses round-robin query routing to balance load across multiple queriers.
+This creates a "checkout line" effect that influences timeout strategy.
+
+> [!Note]
+> #### Concurrent query execution 
+>
+> InfluxDB 3 supports concurrent query execution, which helps minimize the impact of intensive or inefficient queries.
+> However, you should still use appropriate timeouts and optimize your queries for best performance.
+
+### The checkout line analogy
+
+Consider a grocery store with multiple checkout lines:
+- Customers (queries) are distributed across lines (queriers)
+- A slow customer (long-running query) can block others in the same line
+- More checkout lines (queriers) provide more alternatives when retrying
+
+If one querier is unhealthy or has been hijacked by a "noisy neighbor" query (excessively resource hungry), giving up sooner may save time--it's like jumping to a cashier with no customers in line. However, if all queriers are overloaded, then short retries may exacerbate the problem--you wouldn't jump to the end of another line if the cashier is already starting to scan your items.
+
+### Noisy neighbor effects
+
+In distributed systems:
+- A single long-running query can impact other queries on the same querier
+- Shorter timeouts with retries can help queries find less congested queriers
+- The effectiveness depends on the number of available queriers
+
+### When shorter timeouts help
+
+- **Multiple queriers available**: Retries can find less congested queriers
+- **Uneven load distribution**: Some queriers may be significantly less busy
+- **Temporary congestion**: Brief spikes in query load or resource usage
+
+### When shorter timeouts hurt
+
+- **Few queriers**: Limited alternatives for retries
+- **System-wide congestion**: All queriers are equally busy
+- **Expensive query planning**: High overhead for query preparation
+
+## Timeout configuration best practices
+
+### Make timeouts adjustable
+
+Configure timeouts that can be modified without service restarts using environment variables, configuration files, runtime APIs, or per-query overrides. Design your client applications to easily adjust timeouts on the fly, allowing you to respond quickly to performance changes and test different timeout strategies without code changes.
+
+See the [InfluxDB 3 client library examples](#influxdb-3-client-library-examples)
+for how to configure timeouts in Python.
+
+### Use tiered timeout strategies
+
+Implement different timeout classes based on query characteristics.
+
+#### Starting point recommendations
+
+{{% hide-in "cloud-serverless" %}}
+| Query Type | Recommended Timeout | Use Case | Rationale |
+|------------|-------------------|-----------|-----------|
+| UI and dashboard | 10 seconds | Interactive dashboards, real-time monitoring | Users expect immediate feedback |
+| Generic default | 60 seconds | Application queries, APIs | Balances performance and reliability |
+| Mixed workload | 2 minutes | Development, testing environments | Accommodates various query types |
+| Analytical and background | 5 minutes | Reports, batch processing, ETL operations | Complex queries need more time |
+{{% /hide-in %}}
+
+{{% show-in "cloud-serverless" %}}
+| Query Type | Recommended Timeout | Use Case | Rationale |
+|------------|-------------------|-----------|-----------|
+| UI and dashboard | 10 seconds | Interactive dashboards, real-time monitoring | Users expect immediate feedback |
+| Generic default | 30 seconds | Application queries, APIs | Serverless optimized for shorter queries |
+| Mixed workload | 60 seconds | Development, testing environments | Limited by serverless execution model |
+| Analytical and background | 2 minutes | Reports, batch processing | Complex queries within serverless limits |
+{{% /show-in %}}
+
+{{% show-in "enterprise, core" %}}
+> [!Tip]
+> #### Use caching
+> Where immediate feedback is crucial, consider using [Last Value Cache](/influxdb3/version/admin/manage-last-value-caches/) to speed up queries for recent values and [Distinct Value Cache](/influxdb3/version/admin/manage-distinct-value-caches/) to speed up queries for distinct values.
+{{% /show-in %}}
+
+### Implement progressive timeout and retry logic
+
+Consider using more sophisticated retry strategies rather than simple fixed retries:
+
+1. **Exponential backoff**: Increase delay between retry attempts
+2. **Jitter**: Add randomness to prevent thundering herd effects
+3. **Circuit breakers**: Stop retries when system is overloaded
+4. **Deadline propagation**: Respect overall operation deadlines
+
+### Warning signs
+
+Consider these indicators that timeouts may need adjustment:
+
+- **Timeouts > 10 minutes**: Usually indicates [query optimization](/influxdb3/version/query-data/troubleshoot-and-optimize/optimize-queries/) opportunities
+- **High retry rates**: May indicate timeouts are too aggressive
+- **Resource utilization spikes**: Long-running queries may need shorter timeouts
+- **User complaints**: Balance between performance and user experience
+
+### Environment-specific considerations
+
+- **Development**: Use longer timeouts for debugging
+- **Production**: Use shorter timeouts with monitoring
+- **Cost-sensitive**: Use aggressive timeouts and [query optimization](/influxdb3/version/query-data/troubleshoot-and-optimize/optimize-queries/)
+
+### Experimental and ad-hoc queries
+
+When introducing a new query to your application or when issuing ad-hoc queries to a database with many users, your query might be the "noisy neighbor" (the shopping cart overloaded with groceries). By setting a tighter timeout on experimental queries you can reduce the impact on other users.
+
+
+## InfluxDB 3 client library examples
+
+### Python client with timeout configuration
+
+Configure timeouts in the InfluxDB 3 Python client:
+
+```python { placeholders="DATABASE_NAME|HOST_URL|AUTH_TOKEN" }
+import influxdb_client_3 as InfluxDBClient3
+
+# Configure different timeout classes (in seconds)
+ui_timeout = 10      # For dashboard queries  
+api_timeout = 60     # For application queries
+batch_timeout = 300  # For analytical queries
+
+# Create client with default timeout
+client = InfluxDBClient3.InfluxDBClient3(
+    host="https://{{< influxdb/host >}}",
+    database="DATABASE_NAME", 
+    token="AUTH_TOKEN",
+    timeout=api_timeout  # Python client uses seconds
+)
+
+# Quick query with short timeout
+def query_latest_data():
+    try:
+        result = client.query(
+            query="SELECT * FROM sensors WHERE time >= now() - INTERVAL '5 minutes' ORDER BY time DESC LIMIT 10",
+            timeout=ui_timeout
+        )
+        return result.to_pandas()
+    except Exception as e:
+        print(f"Quick query failed: {e}")
+        return None
+
+# Analytical query with longer timeout  
+def query_daily_averages():
+    query = """
+    SELECT 
+        DATE_TRUNC('day', time) as day,
+        room,
+        AVG(temperature) as avg_temp,
+        COUNT(*) as readings
+    FROM sensors 
+    WHERE time >= now() - INTERVAL '30 days'
+    GROUP BY DATE_TRUNC('day', time), room
+    ORDER BY day DESC, room
+    """
+    
+    try:
+        result = client.query(
+            query=query,
+            timeout=batch_timeout
+        )
+        return result.to_pandas()
+    except Exception as e:
+        print(f"Analytical query failed: {e}")
+        return None
+```
+
+Replace the following:
+
+{{% hide-in "cloud-serverless" %}}
+- {{% code-placeholder-key %}}`DATABASE_NAME`{{% /code-placeholder-key %}}: the name of the database to query{{% /hide-in %}}
+{{% show-in "cloud-serverless" %}}
+- {{% code-placeholder-key %}}`DATABASE_NAME`{{% /code-placeholder-key %}}: the name of the bucket to query{{% /show-in %}}
+{{% show-in "clustered,cloud-dedicated" %}}
+- {{% code-placeholder-key %}}`AUTH_TOKEN`{{% /code-placeholder-key %}}: a [database token](/influxdb3/clustered/admin/tokens/#database-tokens) with _read_ access to the specified database.{{% /show-in %}}
+{{% show-in "cloud-serverless" %}}
+- {{% code-placeholder-key %}}`AUTH_TOKEN`{{% /code-placeholder-key %}}:  an [API token](/influxdb3/cloud-serverless/admin/tokens/) with _read_ access to the specified bucket.{{% /show-in %}}
+{{% show-in "enterprise,core" %}}
+- {{% code-placeholder-key %}}`AUTH_TOKEN`{{% /code-placeholder-key %}}: your {{% token-link "database" %}}with read permissions on the specified database{{% /show-in %}}
+
+### Basic retry logic implementation
+
+Implement simple retry strategies with progressive timeouts:
+
+```python
+import time
+import influxdb_client_3 as InfluxDBClient3
+
+def query_with_retry(client, query: str, initial_timeout: int = 60, max_retries: int = 2):
+    """Execute query with basic retry and progressive timeout increase"""
+    
+    for attempt in range(max_retries + 1):
+        # Progressive timeout: increase timeout on each retry
+        timeout_seconds = initial_timeout + attempt * 30
+        
+        try:
+            result = client.query(
+                query=query,
+                timeout=timeout_seconds
+            )
+            return result
+            
+        except Exception as e:
+            if attempt == max_retries:
+                print(f"Query failed after {max_retries + 1} attempts: {e}")
+                raise
+            
+            # Simple backoff delay
+            delay = 2 * (attempt + 1)
+            print(f"Query attempt {attempt + 1} failed: {e}")
+            print(f"Retrying in {delay} seconds with timeout {timeout_seconds}s...")
+            time.sleep(delay)
+    
+    return None
+
+# Usage example
+result = query_with_retry(
+    client=client,
+    query="SELECT * FROM large_table WHERE time >= now() - INTERVAL '1 day'",
+    initial_timeout=60,
+    max_retries=2
+)
+```
+
+## Monitoring and troubleshooting
+
+### Key metrics to monitor
+
+Track these essential timeout-related metrics:
+
+- **Query duration percentiles**: P50, P95, P99 execution times
+- **Timeout rate**: Percentage of queries that time out
+- **Error rates**: Timeout errors vs. other failure types
+- **Resource utilization**: CPU and memory usage during query execution
+
+### Common timeout issues
+
+#### High timeout rates
+
+**Symptoms**: Many queries exceeding timeout limits
+
+**Common causes**:
+- Timeouts set too aggressively for query complexity
+- System resource constraints
+- Inefficient query patterns
+
+**Solutions**:
+1. Analyze query performance patterns
+2. [Optimize slow queries](/influxdb3/version/query-data/troubleshoot-and-optimize/optimize-queries/) or increase timeouts appropriately
+3. Scale system resources
+
+#### Inconsistent query performance
+
+**Symptoms**: Same queries sometimes fast, sometimes timeout
+
+**Common causes**:
+
+- Resource contention from concurrent queries
+- Data compaction state (queries may be faster after compaction completes)
+
+**Solutions**:
+
+1. Analyze query patterns to identify and optimize slow queries
+2. Implement retry logic with exponential backoff in your client applications
+3. Adjust timeout values based on observed query performance patterns
+{{% show-in "enterprise,core" %}}
+4. Implement [Last Value Cache](/influxdb3/version/admin/manage-last-value-caches/) to speed up queries for recent values
+5. Implement [Distinct Value Cache](/influxdb3/version/admin/manage-distinct-value-caches/) to speed up queries for distinct values
+{{% /show-in %}}
+
+> [!Note]
+> Regular analysis of timeout patterns helps identify optimization opportunities and system scaling needs.
\ No newline at end of file