Documentation

Kapacitor

kapacitor flux task update

The kapacitor flux task update command updates a Kapacitor Flux task using a specified file or stdin.

Usage

kapacitor flux task update [flags] [flux-script]

Arguments

  • flux-script: Flux script provided via stdin (-).

Flags

FlagDescription
-f--filePath to Flux script file
-h--helpShow command help
-i--idRequired: Flux task ID
--jsonOutput data as JSON
--statusUpdate the task’s status (active or inactive)

Examples

Update Flux task code using a file

kapacitor flux task update \
  --id 000x00xX0xXXx00 \
  --file /path/to/updated-task.flux

Update Flux task code via stdin

kapacitor flux task update --id 000x00xX0xXXx00 -
# Enter the Flux script in the stdin prompt

Enable or disable a Flux task

kapacitor flux task update \
  --id 000x00xX0xXXx00 \
  --status inactive

Was this page helpful?

Thank you for your feedback!

© 2026 InfluxData, Inc.

Where are you running InfluxDB?

Select your InfluxDB Cloud region and cluster or your InfluxDB OSS URL and we’ll customize code examples for you. Identify your InfluxDB Cloud cluster.

  • InfluxDB Cloud
  • InfluxDB OSS or Enterprise
AWS

  • US West (Oregon)

GCP
Azure
Default
Custom

For more information, see InfluxDB Cloud regions or InfluxDB OSS URLs.

Thank you for your feedback!

Let us know what we can do better:

Thank you!

No thanks

New in InfluxDB 3.8

Key enhancements in InfluxDB 3.8 and the InfluxDB 3 Explorer 1.6.

See the Blog Post

InfluxDB 3.8 is now available for both Core and Enterprise, alongside the 1.6 release of the InfluxDB 3 Explorer UI. This release is focused on operational maturity and making InfluxDB easier to deploy, manage, and run reliably in production.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On April 7, 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