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!


InfluxDB 3.9: Performance upgrade preview

InfluxDB 3 Enterprise 3.9 includes a beta of major performance upgrades with faster single-series queries, wide-and-sparse table support, and more.

InfluxDB 3 Enterprise 3.9 includes a beta of major performance and feature updates.

Key improvements:

  • Faster single-series queries
  • Consistent resource usage
  • Wide-and-sparse table support
  • Automatic distinct value caches for reduced latency with metadata queries

Preview features are subject to breaking changes.

For more information, see:

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:

Telegraf Controller v0.0.6-beta now available

Telegraf Controller v0.0.6-beta is now available with new features, improvements, and bug fixes.

View the release notes
Download Telegraf Controller v0.0.6-beta

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