Documentation

experimental.addDuration() function

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

experimental.addDuration() adds a duration to a time value and returns the resulting time value.

Deprecated

experimental.addDuration() is deprecated in favor of date.add().

Function type signature
(d: duration, to: A, ?location: {zone: string, offset: duration}) => time where A: Timeable

For more information, see Function type signatures.

Parameters

d

(Required) Duration to add.

to

(Required) Time to add the duration to.

location

Location to use for the time value.

Use an absolute time or a relative duration. Durations are relative to now().

Examples

Add six hours to a timestamp

import "experimental"

experimental.addDuration(d: 6h, to: 2019-09-16T12:00:00Z)// Returns 2019-09-16T18:00:00.000000000Z

Add one month to yesterday

A time may be represented as either an explicit timestamp or as a relative time from the current now time. addDuration can support either type of value.

import "experimental"

option now = () => 2021-12-10T16:27:40Z

experimental.addDuration(d: 1mo, to: -1d)// Returns 2022-01-09T16:27:40Z

Add six hours to a relative duration

import "experimental"

option now = () => 2022-01-01T12:00:00Z

experimental.addDuration(d: 6h, to: 3h)// Returns 2022-01-01T21:00:00.000000000Z

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