- influx task retry-failed
- Usage
- Flags
- Examples
- Authentication credentials
- Required permissions
- Retry failed task runs for a specific task ID
- Retry failed task runs that occurred before a specific time
- Retry failed task runs that occurred after a specific time
- Retry failed task runs that occurred in a specific time range
- Retry failed runs for a limited number of tasks
- Retry a limited number of failed runs for a task
- Print information about runs that will be retried
- Related
influx task retry-failed
- influx CLI 2.0.5+
- InfluxDB 2.0.5+
The influx task retry-failed command retries failed InfluxDB task runs.
Usage
1. 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, --orgor--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
- Retry failed task runs that occurred before a specific time
- Retry failed task runs that occurred after a specific time
- Retry failed task runs that occurred in a specific time range
- Retry failed runs for a limited number of tasks
- Retry a limited number of failed runs for a task
- Print information about runs that will be retried
Retry failed task runs for a specific task ID
1. influx task retry-failed \
2. --id 0Xx0oox00XXoxxoo1
Retry failed task runs that occurred before a specific time
1. influx task retry-failed \
2. --before 2021-01-01T00:00:00Z
Retry failed task runs that occurred after a specific time
1. influx task retry-failed \
2. --after 2021-01-01T00:00:00Z
Retry failed task runs that occurred in a specific time range
1. influx task retry-failed \
2. --after 2021-01-01T00:00:00Z \
3. --before 2021-01-01T23:59:59Z
Retry failed runs for a limited number of tasks
1. influx task retry-failed \
2. --task-limit 5
Retry a limited number of failed runs for a task
1. influx task retry-failed \
2. --id 0Xx0oox00XXoxxoo1 \
3. --run-limit 5
Print information about runs that will be retried
1. influx task retry-failed \
2. --dry-run
Related
- Process data with InfluxDB tasks
- influx CLI—Provide required authentication credentials
- influx CLI—Flag patterns and conventions
