Documentation

influx task retry-failed

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

Usage

influx task retry-failed [flags]
  • Copy
  • Fill window

Flags

FlagDescriptionInput typeMaps to ?
--afterRetry task runs that occurred after this time (RFC3339 timestamp)string
-c--active-configCLI configuration to use for commandstring
--configs-pathPath to influx CLI configurations (default ~/.influxdbv2/configs)stringINFLUX_CONFIGS_PATH
--beforeRetry task runs that occurred before this time (RFC3339 timestamp)string
--dry-runPrint information about task runs that would be retried
-h--helpHelp for the list command
--hide-headersHide table headers (default false)INFLUX_HIDE_HEADERS
--hostHTTP address of InfluxDB (default http://localhost:8086)stringINFLUX_HOST
--http-debugInspect communication with InfluxDB servers.string
-i--idTask IDstring
--jsonOutput data as JSON (default false)INFLUX_OUTPUT_JSON
-o--orgTask organization namestringINFLUX_ORG
--org-idTask organization IDstringINFLUX_ORG_ID
--run-limitMaximum number of failed runs to retry per task (1-500, default 100)integer
--skip-verifySkip TLS certificate verificationINFLUX_SKIP_VERIFY
--task-limitMaximum number of tasks to retry failed runs for (1-500, default 100)integer
-t--tokenAPI tokenstringINFLUX_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 All Access token to retry failed tasks.

Retry failed task runs for a specific task ID
influx task retry-failed \
  --id 0Xx0oox00XXoxxoo1
  • Copy
  • Fill window
Retry failed task runs that occurred before a specific time
influx task retry-failed \
  --before 2021-01-01T00:00:00Z
  • Copy
  • Fill window
Retry failed task runs that occurred after a specific time
influx task retry-failed \
  --after 2021-01-01T00:00:00Z
  • Copy
  • Fill window
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
  • Copy
  • Fill window
Retry failed runs for a limited number of tasks
influx task retry-failed \
  --task-limit 5
  • Copy
  • Fill window
Retry a limited number of failed runs for a task
influx task retry-failed \
  --id 0Xx0oox00XXoxxoo1 \
  --run-limit 5
  • Copy
  • Fill window
influx task retry-failed \
  --dry-run
  • Copy
  • Fill window

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 3 Core and Enterprise are now in Beta

InfluxDB 3 Core and Enterprise are now available for beta testing, available under MIT or Apache 2 license.

InfluxDB 3 Core is a high-speed, recent-data engine that collects and processes data in real-time, while persisting it to local disk or object storage. InfluxDB 3 Enterprise is a commercial product that builds on Core’s foundation, adding high availability, read replicas, enhanced security, and data compaction for faster queries. A free tier of InfluxDB 3 Enterprise will also be available for at-home, non-commercial use for hobbyists to get the full historical time series database set of capabilities.

For more information, check out:

InfluxDB Cloud powered by TSM