tencent cloud

Tencent Cloud WeData

Development and Ops System Tables

PDF
Focus Mode
Font Size
Last updated: 2026-04-24 16:39:59

Usage Requirements

Before accessing and using the WeData system, the following conditions must be met:
1. Data source requirements: must use DLC Data Source. Other data sources temporary not support system table capacity.
2. Catalog requirements: must use tc-catalog to access system tables.

System Table List Overview

WeData supports two scheduling modes: Task Scheduling and Workflow Scheduling. Both modes are configured during project creation and cannot be modified. The available system tables vary under different scheduling modes.

Task Scheduling Mode

The system table provided by the scheduling mode and its update frequency are as follows:
Table name
Description(Optional)
Update Frequency
task
Contains the basic information of tasks in the orchestration space (development status).
5 minutes.
task_schedule
Contains the scheduling info of tasks in the orchestration space (development status).
5 minutes.
task_dependency
Contains the dependency relationship of tasks in the orchestration space (development status).
5 minutes.
workflow
Contains the basic information of workflows in the orchestration space (development status).
5 minutes.
task_run_record
Contains the run history of all instances in the Ops center.
5 minutes.
parameter
Parameter table, including project parameter, workflow parameter, and task parameter (workflow and task parameters are in development status).
5 minutes.

Workflow Scheduling Mode

The system table provided by workflow scheduling mode and its update frequency are as follows:
Table name
Description(Optional)
Update Frequency
trigger_task
Contains the basic information of tasks in workflow scheduling mode (development status).
5 minutes.
trigger_workflow
Contains the basic information and scheduling configuration of workflows in workflow scheduling mode (development status).
5 minutes.
trigger_workflow_schedule
Contains the scheduling information of workflows in workflow scheduling mode.
5 minutes.
trigger_task_run_record
Contains the record information of task runs in workflow scheduling mode.
5 minutes.
trigger_workflow_run_record
Contains the run history of workflows in workflow scheduling mode.
5 minutes.
parameter
Parameter table, including project parameter, workflow parameter, and task parameter (workflow and task parameters are in development status).
5 minutes.

Detailed Description of System Table (Task Scheduling Mode)

task (Basic task Information)

Table path: system_catalog.wedata.task
Field structure:
Column Name
Data Type
Description(Optional)
project_id
string
Project ID
project_name
string
Project Name
task_id
string
Task ID
task_name
string
Task name
task_type
string
Task type
status
string
Task Status
owner
string
Task Owner
workflow_id
string
Associated workflow ID
workflow_name
string
Workflow name
schedule_frequency
string
Scheduling frequency
create_timestamp
timestamp_tz(6)
Task creation time.
last_update_timestamp
timestamp_tz(6)
Last update time.
last_update_user
string
Last updated user
data_source
string
Data Source
dlc_data_engine
string
DLC Data Engine
dlc_resource_group
string
DLC Resource Group
execution_resource_group
string
Execution Resource Group
Query Example:
Query tasks under a specific project leader.
SELECT
task_id,
task_name,
task_type,
status,
workflow_name
FROM
wedata.task
WHERE
project_id = 'your_project_id' -- Replace with your project ID
AND owner = 'your_owner_name'; -- Replace with your owner name

task_schedule (Task Scheduling Information)

Table path: system_catalog.wedata.task_schedule
Field structure:
Column Name
Data Type
Description(Optional)
project_id
string
Project ID
project_name
string
Project Name
task_id
string
Task ID
task_name
string
Task name
config_method
string
Task associated workflow type:<br>PERIODICALLY: Periodic workflow<br>MANUALLY: Manual workflow
schedule_cycle_type
string
Scheduling configuration method:<br>COMMON: General configuration<br>CRON_EXPRESSION: Use cron expression configuration
effective_start_time
timestamp_tz(6)
Effective time - Start time
effective_end_time
timestamp_tz(6)
Effective time - End time
schedule_frequency
string
Scheduling cycle:<br>ONEOFF_CYCLE: One-time<br>YEAR_CYCLE: Year<br>MONTH_CYCLE: Month<br>WEEK_CYCLE: Week<br>DAY_CYCLE: Day<br>HOUR_CYCLE: Hour<br>MINUTE_CYCLE: Minute<br>CRONTAB_CYCLE: crontab expression type
delay_time
long
Scheduling delay time, in minutes:<br>For minute-based tasks, this field is 0, means no delay.<br>For hourly tasks, it refers to a delay of a few minutes per hour starting at 0 minute.<br>For daily, weekly, monthly, and yearly tasks, it indicates a delay of a few minutes starting at 0:00.
execution_start_time
string
Execution time - Start time
execution_end_time
string
Execution time - End time
cycle_step
long
Scheduling frequency:<br>For example, for minute-based tasks, 20 means scheduling every 20 minutes.<br>For daily tasks, 1 means scheduling once a day.
time_point
string
Specify scheduling time<br>For example, configuration when specifying running time for hourly scheduling tasks
time_zone
string
Scheduling timezone
cron
string
cron expression, only for tasks with cron configuration mode
Query Example:
Query the task list with a scheduling cycle of one day in the specified project.
SELECT
project_id,
project_name,
task_id,
task_name,
config_method,
schedule_cycle_type,
effective_start_time,
effective_end_time,
schedule_frequency
FROM
wedata.task_schedule
WHERE
project_id = 'your_project_id' -- Replace with your project ID
AND schedule_frequency = 'DAY_CYCLE';

task_dependency (Task Dependency)

Table path: system_catalog.wedata.task_dependency
Field structure:
Column Name
Data Type
Description(Optional)
project_id
string
Project ID
project_name
string
Project Name
task_id
string
Task ID
task_name
string
Task name
dependency_project_id
string
Upstream task associated project ID
dependency_project_name
string
Upstream task associated project name
dependency_task_id
string
Upstream task ID
dependency_task_name
string
Upstream Task Name
Query Example:
Retrieve the direct upstream task of a task.
SELECT
dependency_project_id AS upstream_project_id,
dependency_project_name AS upstream_project_name,
dependency_task_id AS upstream_task_id,
dependency_task_name AS upstream_task_name
FROM
wedata.task_dependency
WHERE
task_id = 'your_task_id'; -- Replace with your task ID

workflow (Basic Workflow Information)

Table path: system_catalog.wedata.workflow
Field structure:
Column Name
Data Type
Description(Optional)
project_id
string
Project ID
project_name
string
Project Name
workflow_id
string
Associated workflow ID
workflow_name
string
Workflow name
workflow_type
string
Workflow type: Workflow cycle/Manual workflow
folder
string
Workflow folder
create_time
timestamp_tz(6)
Workflow creation time
last_update_timestamp
timestamp_tz(6)
Last update time.
last_update_user
string
Latest updater
owner
string
workflow owner
Query Example:
Query the workflow list under a specific user’s name.
SELECT
workflow_id,
workflow_name,
workflow_type
FROM
wedata.workflow
WHERE
owner = 'your_owner_name'; -- Replace with your owner name

task_run_record (Task Instance Run History)

Table path: system_catalog.wedata.task_run_record
Field structure:
Column Name
Data Type
Description(Optional)
task_run_id
string
Task instance ID
task_id
string
Task ID
task_name
string
Task name
project_id
string
Task associated project ID
project_name
string
Task associated project name
workflow_id
string
Associated workflow ID
workflow_name
string
workflow name
dp_data_dt
timestamp_tz(6)
Planned Scheduling Time
task_run_status
string
Instance State
run_min
string
Runtime
run_start_dttm
timestamp_tz(6)
start time
run_end_dttm
timestamp_tz(6)
running end time
run_log_url
string
Instance Details Page - Execution Log Product Link
task_run_error_msg
string
Critical Error Log
last_update_timestamp
timestamp_tz(6)
Last update time.
last_update_user
string
Latest updater
Query Example:
Example 1: Count the number of run attempts for each workflow task instance in the past 7 days.
SELECT
workflow_name,
COUNT(task_run_id) AS instance_count
FROM
wedata.task_run_record
WHERE
run_start_dttm >= CURRENT_DATE - INTERVAL '7' DAY
GROUP BY
workflow_name;
Example 2: Get the 10 tasks with the longest average running time.
SELECT
task_name,
AVG(run_min) AS avg_run_min
FROM
wedata.task_run_record
WHERE
run_min IS NOT NULL
GROUP BY
task_name
ORDER BY
avg_run_min DESC
LIMIT 10;

parameter (Parameter Information)

Table path: system_catalog.wedata.parameter
Note:
The parameter information table can be used in task scheduling mode and workflow scheduling mode, with the same table structure.
Field structure:
Column Name
Data Type
Description(Optional)
name
string
Project/Task/Workflow Name
id
string
Project/Task/Workflow ID
level
string
Parameter Level:<br>TASK: Task Level<br>PROJECT: Project Level<br>WORKFLOW: Workflow Level
param_name
string
Parameter Name
param_value_dev
string
Parameter Value in Development Status
param_value_prod
string
Parameter Value in Production Status
Query Example:
Retrieve parameters used in the task and its value (including parameter parsing at the task, workflow and project level).
WITH task_params AS (
SELECT
p.param_name,
p.param_value_dev AS dev_value,
p.param_value_prod AS prod_value,
'TASK' AS param_level
FROM
wedata.parameter p
JOIN
wedata.task t ON p.id = t.task_id
WHERE
t.task_id = 'task_id' -- Replace with your task ID
AND p.level = 'TASK'
),
workflow_params AS (
SELECT
p.param_name,
p.param_value_dev AS dev_value,
p.param_value_prod AS prod_value,
'WORKFLOW' AS param_level
FROM
wedata.parameter p
JOIN
wedata.task t ON p.id = t.workflow_id
WHERE
t.task_id = 'task_id' -- Replace with your task ID
AND p.level = 'WORKFLOW'
),
project_params AS (
SELECT
p.param_name,
p.param_value_dev AS dev_value,
p.param_value_prod AS prod_value,
'PROJECT' AS param_level
FROM
wedata.parameter p
JOIN
wedata.task t ON p.id = t.project_id
WHERE
t.task_id = 'task_id' -- Replace with your task ID
AND p.level = 'PROJECT'
),
all_params AS (
SELECT * FROM task_params
UNION ALL
SELECT * FROM workflow_params
UNION ALL
SELECT * FROM project_params
)
SELECT
param_name,
dev_value,
prod_value,
param_level
FROM (
SELECT
param_name,
dev_value,
prod_value,
param_level,
ROW_NUMBER() OVER (
PARTITION BY param_name
ORDER BY CASE
WHEN param_level = 'TASK' THEN 1
WHEN param_level = 'WORKFLOW' THEN 2
WHEN param_level = 'PROJECT' THEN 3
END
) AS rn
FROM
all_params
) ranked_params
WHERE
rn = 1;

Detailed Description of System Table (Workflow Scheduling Mode)

Note:
The following system tables are available only in projects in workflow scheduling mode. In workflow scheduling mode, scheduling configuration is performed at workflow granularity, and task granularity cannot be configured for scheduling. All tables are responsible for and created by System user, and modifications are not allowed.

trigger_task (Basic Workflow Scheduling Task Information)

Table path: system_catalog.wedata.trigger_task
Description: Contains the basic information of tasks in the orchestration space in workflow scheduling mode (development status).
Field structure:
Column Name
Data Type
Description(Optional)
project_id
string
Project ID
project_name
string
Project Name
task_id
string
Task ID
task_name
string
Task name
task_type
string
Task type
owner
string
Task Owner
workflow_name
string
Workflow name
workflow_id
string
Associated workflow ID
create_timestamp
timestamp_tz(6)
Task creation time.
last_update_timestamp
timestamp_tz(6)
Last update time.
last_update_user
string
Last updated user
data_source
string
Data Source Name
dlc_data_engine
string
DLC Data Engine
execution_resource_group
string
Resource group (scheduling resource group or integration resource group)
dlc_resource_group
string
DLC Resource Group
Query Example:
Query all tasks under a specific project leader in a specified project.
SELECT
task_id,
task_name,
task_type,
workflow_name,
workflow_id
FROM
wedata.trigger_task
WHERE
project_id = 'your_project_id' -- Replace with your project ID
AND owner = 'your_owner_name'; -- Replace with your owner name
Query all tasks under a specific workflow.
SELECT
task_id,
task_name,
task_type,
owner,
data_source,
execution_resource_group
FROM
wedata.trigger_task
WHERE
workflow_id = 'your_workflow_id'; -- Replace with your workflow ID

trigger_workflow (Workflow Scheduling Information and Scheduling Configuration)

Table path: system_catalog.wedata.trigger_workflow
Description: Contains the basic information and scheduling configuration of workflows in workflow scheduling mode (development status). Scheduling configuration is performed at workflow granularity, hence scheduling-related fields are integrated into the Workflow Table.
Field structure:
Column Name
Data Type
Description(Optional)
project_id
string
Project ID
project_name
string
Project Name
workflow_id
string
Workflow ID.
workflow_name
string
Workflow name
workflow_type
string
Workflow type: Cycle/Manual
folder
string
Workflow folder
create_time
timestamp_tz(6)
Workflow creation time
last_update_timestamp
timestamp_tz(6)
Last update time.
last_update_user
string
Last updated user
owner
string
workflow owner
trigger_method
string
Triggering method (scheduled trigger/file arrival trigger)
schedule_cycle_type
string
Configuration mode: General/cron
schedule_frequency
string
Scheduling frequency
time_zone
string
Scheduling timezone
effective_start_time
timestamp_tz(6)
Effective time - Start time
effective_end_time
timestamp_tz(6)
Effective time - End time
execution_time
string
Execution Time
cron
string
cron expression, only for workflows with cron configuration mode
Note:
trigger_workflow contains both workflow basic information and scheduling configuration message. The trigger_method field identifier indicates the trigger mode, supporting two methods: scheduled trigger and file arrival trigger.
Query Example:
Query the workflow and scheduling configuration under a specific user’s name.
SELECT
workflow_id,
workflow_name,
trigger_method,
schedule_frequency,
time_zone,
cron
FROM
wedata.trigger_workflow
WHERE
owner = 'your_owner_name'; -- Replace with your owner name
Query all workflows using scheduled trigger.
SELECT
workflow_id,
workflow_name,
schedule_frequency,
effective_start_time,
effective_end_time,
execution_time,
time_zone
FROM
wedata.trigger_workflow
WHERE
project_id = 'your_project_id' -- Replace with your project ID
AND trigger_method = 'scheduled trigger';
Query workflows configured with cron expression.
SELECT
workflow_id,
workflow_name,
cron,
time_zone,
effective_start_time,
effective_end_time
FROM
wedata.trigger_workflow
WHERE
project_id = 'your_project_id' -- Replace with your project ID
AND schedule_cycle_type = 'cron';

trigger_workflow_schedule (Workflow Scheduling Information)

Table path: system_catalog.wedata.trigger_workflow_schedule
Description: Contains the scheduling information of workflows in workflow scheduling mode.
Field structure:
Column Name
Data Type
Description(Optional)
project_id
string
Project ID
project_name
string
Project Name
workflow_id
string
Workflow ID.
workflow_name
string
Workflow name
trigger_id
string
Trigger ID
trigger_method
string
Triggering method
schedule_cycle_type
string
Configuration Method
schedule_frequency
string
Scheduling frequency
time_zone
string
Scheduling timezone
effective_start_time
timestamp_tz(6)
Effective time - Start time
effective_end_time
timestamp_tz(6)
Effective time - End time
cron
string
Cron Expression
file_arrival_path
string
File arrival path
trigger_minimum_interval_second
long
Minimum trigger interval (second).
trigger_wait_time_second
long
Trigger waiting time (second).
last_update_timestamp
timestamp_tz(6)
Last update time.
last_update_user
string
Last updated user
Query Example:
Query the scheduling configuration message of ALL workflows in the specified project.
SELECT
workflow_id,
workflow_name,
trigger_id,
trigger_method,
schedule_frequency,
cron,
time_zone
FROM
wedata.trigger_workflow_schedule
WHERE
project_id = 'your_project_id'; -- Replace with your project ID
Query all workflow scheduling configurations that use file arrival triggers.
SELECT
workflow_id,
workflow_name,
trigger_id,
file_arrival_path,
trigger_minimum_interval_second,
trigger_wait_time_second
FROM
wedata.trigger_workflow_schedule
WHERE
project_id = 'your_project_id' -- Replace with your project ID
AND trigger_method = 'file arrival trigger';
Query workflow scheduling info configured with cron expression.
SELECT
workflow_id,
workflow_name,
trigger_id,
cron,
time_zone,
effective_start_time,
effective_end_time
FROM
wedata.trigger_workflow_schedule
WHERE
project_id = 'your_project_id' -- Replace with your project ID
AND schedule_cycle_type = 'cron';

trigger_task_run_record (Workflow Scheduling Task Run History)

Table path: system_catalog.wedata.trigger_task_run_record
Description: Contains the record information of task runs in workflow scheduling mode.
Field structure:
Column Name
Data Type
Description(Optional)
task_run_id
string
Task run ID
task_id
string
Task ID
task_name
string
Task name
project_id
string
Task associated project ID
project_name
string
Task associated project name
workflow_id
string
Associated workflow ID
workflow_name
string
workflow name
task_run_status
string
Task running status.
run_min
string
Runtime
run_start_dttm
timestamp_tz(6)
start time
run_end_dttm
timestamp_tz(6)
running end time
run_log_url
string
Task Execution Details Page - Execution Log Product Link
task_run_error_msg
string
Critical Error Log
last_update_timestamp
timestamp_tz(6)
Last update time.
last_update_user
string
Last updated user
Query Example:
Example 1: Count the number of run attempts for each task in the workflow in the past 7 days.
SELECT
workflow_name,
COUNT(task_run_id) AS run_count
FROM
wedata.trigger_task_run_record
WHERE
run_start_dttm >= CURRENT_DATE - INTERVAL '7' DAY
GROUP BY
workflow_name;
Example 2: Get the 10 tasks with the longest average running time.
SELECT
task_name,
AVG(run_min) AS avg_run_min
FROM
wedata.trigger_task_run_record
WHERE
run_min IS NOT NULL
GROUP BY
task_name
ORDER BY
avg_run_min DESC
LIMIT 10;
Example 3: Query failed tasks and their error logs.
SELECT
task_run_id,
task_name,
workflow_name,
task_run_status,
run_start_dttm,
run_end_dttm,
task_run_error_msg
FROM
wedata.trigger_task_run_record
WHERE
project_id = 'your_project_id' -- Replace with your project ID
AND task_run_status = 'fail';

trigger_workflow_run_record (Workflow Run History)

Table path: system_catalog.wedata.trigger_workflow_run_record
Description: Contains the run history of workflows in workflow scheduling mode. This is a newly-added system table in workflow scheduling mode to record the execution situation of each workflow run, including periodic scheduling trigger and manual triggering.
Field structure:
Column Name
Data Type
Description(Optional)
project_id
string
Project ID
project_name
string
Project Name
workflow_id
string
Workflow ID.
workflow_name
string
Workflow name
workflow_run_id
string
Workflow run ID
workflow_run_status
string
Workflow execution status (Waiting/running/success/failure)
run_min
string
Runtime
run_start_dttm
timestamp_tz(6)
start time
run_end_dttm
timestamp_tz(6)
running end time
trigger_method
string
Trigger mode (manual trigger/scheduling trigger)
run_log_url
string
Workflow run detail page link
last_update_timestamp
timestamp_tz(6)
Last update time.
last_update_user
string
Last updated user
Query Example:
Example 1: Query a specific workflow's execution history.
SELECT
workflow_run_id,
workflow_run_status,
trigger_method,
run_start_dttm,
run_end_dttm,
run_min
FROM
wedata.trigger_workflow_run_record
WHERE
workflow_id = 'your_workflow_id' -- Replace with your workflow ID
ORDER BY
run_start_dttm DESC;
Example 2: Calculate the success rate of workflow running in the past 7 days.
SELECT
workflow_name,
COUNT(*) AS total_runs,
SUM(CASE WHEN workflow_run_status = 'success' THEN 1 ELSE 0 END) AS success_count,
ROUND(
SUM(CASE WHEN workflow_run_status = 'success' THEN 1 ELSE 0 END) * 100.0 / COUNT(*), 2
) AS success_rate
FROM
wedata.trigger_workflow_run_record
WHERE
run_start_dttm >= CURRENT_DATE - INTERVAL '7' DAY
GROUP BY
workflow_name
ORDER BY
success_rate ASC;
Example 3: Get the 10 workflows with the longest average running time.
SELECT
workflow_name,
AVG(run_min) AS avg_run_min,
COUNT(*) AS run_count
FROM
wedata.trigger_workflow_run_record
WHERE
run_min IS NOT NULL
GROUP BY
workflow_name
ORDER BY
avg_run_min DESC
LIMIT 10;
Example 4: Query failed workflows and their detail links.
SELECT
workflow_run_id,
workflow_name,
trigger_method,
run_start_dttm,
run_end_dttm,
run_log_url
FROM
wedata.trigger_workflow_run_record
WHERE
project_id = 'your_project_id' -- Replace with your project ID
AND workflow_run_status = 'fail'
ORDER BY
run_start_dttm DESC;

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback