Documentation

Troubleshoot queries

Troubleshoot SQL and InfluxQL queries that return unexpected results.

Why doesn’t my query return data?

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. See 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:

    SELECT array_to_string(array_agg([1, 2, 3]), ', ')

If a query times out or returns an error, it might be due to the following:

  • a bad request
  • a server or network problem
  • it queries too much data

Understand Arrow Flight responses and error messages for queries.

Optimize slow or expensive queries

If a query is slow or uses too many compute resources, limit the amount of data that it queries.

See how to optimize queries.

Analyze your queries

Use the following tools to retrieve system query information, analyze query execution, and find performance bottlenecks:

Request help to troubleshoot queries

Some bottlenecks may result from suboptimal query execution plans and are outside your control–for example:

  • Sorting (ORDER BY) data that is already sorted
  • Retrieving numerous small Parquet files from the object store, instead of fewer, larger files
  • Querying many overlapped Parquet files
  • Performing a high number of table scans

If you’ve followed steps to optimize and troubleshoot a query, but it still doesn’t meet performance requirements, request help troubleshooting. Customers with an InfluxDB Cloud Serverless annual or support contract can contact InfluxData Support for assistance.

Query trace logging

Currently, customers cannot enable trace logging for InfluxDB Cloud Serverless clusters. InfluxData engineers can use query plans and trace logging to help pinpoint performance bottlenecks in a query.

If you’ve followed steps to optimize and troubleshoot a query, but it still doesn’t meet performance requirements, request help troubleshooting. Customers with an InfluxDB Cloud Serverless annual or support contract can contact InfluxData Support for assistance.


Was this page helpful?

Thank you for your feedback!


New in InfluxDB 3.5

Key enhancements in InfluxDB 3.5 and the InfluxDB 3 Explorer 1.3.

See the Blog Post

InfluxDB 3.5 is now available for both Core and Enterprise, introducing custom plugin repository support, enhanced operational visibility with queryable CLI parameters and manual node management, stronger security controls, and general performance improvements.

InfluxDB 3 Explorer 1.3 brings powerful new capabilities including Dashboards (beta) for saving and organizing your favorite queries, and cache querying for instant access to Last Value and Distinct Value caches—making Explorer a more comprehensive workspace for time series monitoring and analysis.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On November 3, 2025, the latest tag for InfluxDB Docker images will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments.

If using Docker to install and run InfluxDB, the latest tag will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments. For example, if using Docker to run InfluxDB v2, replace the latest version tag with a specific version tag in your Docker pull command–for example:

docker pull influxdb:2

InfluxDB Cloud Serverless