task_runs

task_runs provides information about the execution of asynchronous tasks.

The following fields are provided in task_runs:

Field	Description
QUERY_ID	ID of the query.
TASK_NAME	Name of the task.
CREATE_TIME	Time when the task was created.
FINISH_TIME	Time when the task finished.
STATE	State of the task. Valid values: PENDING, RUNNING, FAILED, SUCCESS, MERGED, and SKIPPED. MERGED is for materialized view refresh tasks. When a new refresh task is submitted and the old task is still in the pending queue, these tasks will be merged and their priority level will be maintained. SKIPPED is for materialized view refresh tasks. When no data changes are detected on the base table partition, the refresh for the corresponding materialized view partition is skipped.
CATALOG	Catalog where the task belongs.
DATABASE	Database where the task belongs.
DEFINITION	SQL definition of the task.
EXPIRE_TIME	Time when the task expires.
ERROR_CODE	Error code of the task.
ERROR_MESSAGE	Error message of the task.
PROGRESS	The progress of the task.
EXTRA_MESSAGE	Extra message for the task, for example, the partition information in an asynchronous materialized view creation task.
PROPERTIES	Properties of the task.
JOB_ID	Job ID of the task.
PROCESS_TIME	Process time of the task.

A task run record is produced by either SUBMIT TASK or CREATE MATRIALIZED VIEW.

note

A materialized view operation may generate multi task runs, and each task run represents a refresh sub-task which is split in accordance with the partition_refresh_number configuration.

EXTRA_MESSAGE

For a materialized view task run, EXTRA_MESSAGE field will contain the materialized view task run's detail messages, you can find more details in materialized_view_task_run_details.