Documentation

influx task retry-failed

The influx task retry-failed command retries failed InfluxDB task runs.

Usage

influx task retry-failed [flags]

Flags

Flag Description Input type Maps to ?
--after Retry task runs that occurred after this time (RFC3339 timestamp) string
-c --active-config CLI configuration to use for command string
--configs-path Path to influx CLI configurations (default ~/.influxdbv2/configs) string INFLUX_CONFIGS_PATH
--before Retry task runs that occurred before this time (RFC3339 timestamp) string
--dry-run Print information about task runs that would be retried
-h --help Help for the list command
--hide-headers Hide table headers (default false) INFLUX_HIDE_HEADERS
--host HTTP address of InfluxDB (default http://localhost:8086) string INFLUX_HOST
--http-debug Inspect communication with InfluxDB servers. string
-i --id Task ID string
--json Output data as JSON (default false) INFLUX_OUTPUT_JSON
-o --org Task organization name string INFLUX_ORG
--org-id Task organization ID string INFLUX_ORG_ID
--run-limit Maximum number of failed runs to retry per task (1-500, default 100) integer
--skip-verify Skip TLS certificate verification INFLUX_SKIP_VERIFY
--task-limit Maximum number of tasks to retry failed runs for (1-500, default 100) integer
-t --token API token string INFLUX_TOKEN

Examples

Authentication credentials

The examples below assume your InfluxDB host, organization, and token are provided by either the active influx CLI configuration or by environment variables (INFLUX_HOST, INFLUX_ORG, and INFLUX_TOKEN). If you do not have a CLI configuration set up or the environment variables set, include these required credentials for each command with the following flags:

  • --host: InfluxDB host
  • -o, --org or --org-id: InfluxDB organization name or ID
  • -t, --token: InfluxDB API token

Required permissions

Use an Operator or All Access token to retry failed tasks.

Retry failed task runs for a specific task ID
influx task retry-failed \
  --id 0Xx0oox00XXoxxoo1
Retry failed task runs that occurred before a specific time
influx task retry-failed \
  --before 2021-01-01T00:00:00Z
Retry failed task runs that occurred after a specific time
influx task retry-failed \
  --after 2021-01-01T00:00:00Z
Retry failed task runs that occurred in a specific time range
influx task retry-failed \
  --after 2021-01-01T00:00:00Z \
  --before 2021-01-01T23:59:59Z
Retry failed runs for a limited number of tasks
influx task retry-failed \
  --task-limit 5
Retry a limited number of failed runs for a task
influx task retry-failed \
  --id 0Xx0oox00XXoxxoo1 \
  --run-limit 5
influx task retry-failed \
  --dry-run

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.

Read more

InfluxDB v3 enhancements and InfluxDB Clustered is now generally available

New capabilities, including faster query performance and management tooling advance the InfluxDB v3 product line. InfluxDB Clustered is now generally available.

InfluxDB v3 performance and features

The InfluxDB v3 product line has seen significant enhancements in query performance and has made new management tooling available. These enhancements include an operational dashboard to monitor the health of your InfluxDB cluster, single sign-on (SSO) support in InfluxDB Cloud Dedicated, and new management APIs for tokens and databases.

Learn about the new v3 enhancements


InfluxDB Clustered general availability

InfluxDB Clustered is now generally available and gives you the power of InfluxDB v3 in your self-managed stack.

Talk to us about InfluxDB Clustered