View task run history and logs

This page documents an earlier version of InfluxDB. InfluxDB v2.7 is the latest stable version. View this page in the v2.7 documentation.

When an InfluxDB task runs, a “run” record is created in the task’s history. Logs associated with each run provide relevant log messages, timestamps, and the exit status of the run attempt.

Use the InfluxDB user interface (UI) or the influx command line interface (CLI) to view task run histories and associated logs.

View a task’s run history in the InfluxDB UI

  1. In the navigation menu on the left, select Tasks.

  2. Click the name of the task to view the run history.

View task run logs

To view logs associated with a run, click View Logs next to the run in the task’s run history.

View a task’s run history with the influx CLI

Use the influx task run list command to view a task’s run history.

# List all tasks to find the ID of the task to run
influx task list

# Use the task ID to view the run history of a task
influx task run list --task-id=0000000000000000

Detailed run logs are not currently available in the influx CLI.

Retry failed task runs

Use the influx task retry-failed command to retry failed task runs.

# Retry failed tasks for a specific task
influx task retry-failed \
  --id 0000000000000000

# Print information about runs that will be retried
influx task retry-failed \

# 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

Was this page helpful?

Thank you for your feedback!

Set your InfluxDB URL

Introducing InfluxDB 3.0

The new core of InfluxDB built with Rust and Apache Arrow. Available today in InfluxDB Cloud Dedicated.

Learn more

State of the InfluxDB Cloud Serverless documentation

The new documentation for InfluxDB Cloud Serverless is a work in progress. We are adding new information and content almost daily. Thank you for your patience!

If there is specific information you’re looking for, please submit a documentation issue.