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!


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