Documentation

kapacitor flux task retry-failed

The kapacitor flux task retry-failed command retries failed Kapacitor Flux task runs.

Usage

kapacitor flux task retry-failed [flags]

Aliases

  • rtf

Flags

FlagDescription
--afterRetry failed runs that occurred after this time (RFC3339 timestamp)
--beforeRetry failed runs that occurred before this time (RFC3339 timestamp)
--dry-runOutput information about runs that would be retried without retrying the failed runs
-h--helpShow command help
-i--idFlux task ID
--jsonOutput data as JSON
--run-limitMaximum number of failed runs to retry per task (default is 100)
--task-limitMaximum number of tasks to retry failed runs for (default is 100)

Examples

Retry failed Flux task runs for all tasks

kapacitor flux task retry-failed

Retry failed Flux task runs for a specific task

kapacitor flux task retry-failed --id 000x00xX0xXXx00

Retry Flux task runs that failed in a specific time range

kapacitor flux task retry-failed \
  --after 2023-01-01T00:00:00Z \
  --before 2023-01-31T00:00:00Z

View information about failed runs that would be executed

kapacitor flux task retry-failed --dry-run

Limit the number of tasks to retry failed runs for

kapacitor flux task retry-failed --task-limit 10

Limit the number of failed runs to retry for each task

kapacitor flux task retry-failed --run-limit 10

Was this page helpful?

Thank you for your feedback!


Telegraf Enterprise now in public beta

Get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

See the Blog Post

The upcoming Telegraf Enterprise offering is for organizations running Telegraf at scale and is comprised of two key components:

  • Telegraf Controller: A control plane (UI + API) that centralizes Telegraf configuration management and agent health visibility.
  • Telegraf Enterprise Support: Official support for Telegraf Controller and Telegraf plugins.

Join the Telegraf Enterprise beta to get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

For more information:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On May 27, 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