Documentation

experimental.chain() function

experimental.chain() is subject to change at any time.

experimental.chain() runs two queries in a single Flux script sequentially and outputs the results of the second query.

Flux typically executes multiple queries in a single script in parallel. Running the queries sequentially ensures any dependencies the second query has on the results of the first query are met.

Applicable use cases
  • Write to an InfluxDB bucket and query the written data in a single Flux script.

    _Note: experimental.chain() does not guarantee that data written to InfluxDB is immediately queryable. A delay between when data is written and when it is queryable may cause a query using experimental.chain() to fail.

  • Execute queries sequentially in testing scenarios.

Function type signature
(first: stream[A], second: stream[B]) => stream[B] where A: Record, B: Record

For more information, see Function type signatures.

Parameters

first

(Required) First query to execute.

second

(Required) Second query to execute.

Examples

Write to a bucket and query the written data

import "experimental"

downsampled_max =
    from(bucket: "example-bucket-1")
        |> range(start: -1d)
        |> filter(fn: (r) => r._measurement == "example-measurement")
        |> aggregateWindow(every: 1h, fn: max)
        |> to(bucket: "downsample-1h-max", org: "example-org")

average_max =
    from(bucket: "downsample-1h-max")
        |> range(start: -1d)
        |> filter(fn: (r) => r.measurement == "example-measurement")
        |> mean()

experimental.chain(first: downsampled_max, second: average_max)

Was this page helpful?

Thank you for your feedback!


New in InfluxDB 3.6

Key enhancements in InfluxDB 3.6 and the InfluxDB 3 Explorer 1.4.

See the Blog Post

InfluxDB 3.6 is now available for both Core and Enterprise. This release introduces the 1.4 update to InfluxDB 3 Explorer, featuring the beta launch of Ask AI, along with new capabilities for simple startup and expanded functionality in the Processing Engine.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On February 3, 2026, 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