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!


The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Flux is going into maintenance mode and will not be supported in InfluxDB 3.0. This was a decision based on the broad demand for SQL and the continued growth and adoption of InfluxQL. We are continuing to support Flux for users in 1.x and 2.x so you can continue using it with no changes to your code. If you are interested in transitioning to InfluxDB 3.0 and want to future-proof your code, we suggest using InfluxQL.

For information about the future of Flux, see the following: