Documentation

Retry failed Kapacitor Flux tasks

Use the kapacitor flux task retry-failed command to retry failed Kapacitor Flux task runs. Provide the following flags:

  • -i, --id: task ID
  • --before: Retry failed runs that occurred before this time (RFC3339 timestamp)
  • --after: Retry failed runs that occurred after this time (RFC3339 timestamp)
  • --dry-run: Output information about runs that would be retried without retrying the failed runs.
  • --task-limit: Limit the number of tasks to retry failed runs for (default: 100)
  • --run-limit: Limit the number of failed runs to retry per task (default: 100)

Rerun failed tasks with the Kapacitor API

The kapacitor flux task retry-failed command is a convenience command that identifies failed task runs and attempts to run them again. The Kapacitor API doesn’t provide a single endpoint for this functionality, but this process can be accomplished through a series of API calls. For more information, see Manage Flux task runs.

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 2021-01-01T00:00:00Z \
  --before 2021-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!


Introducing InfluxDB Clustered

A highly available InfluxDB 3.0 cluster on your own infrastructure.

InfluxDB Clustered is a highly available InfluxDB 3.0 cluster built for high write and query workloads on your own infrastructure.

InfluxDB Clustered is currently in limited availability and is only available to a limited group of InfluxData customers. If interested in being part of the limited access group, please contact the InfluxData Sales team.

Learn more
Contact InfluxData Sales

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: