The drawer on the right side of the workflow details page provides workflow-level general configuration items. In addition to scheduling and parameters, this section introduces the following items: basic information, tags, monitoring metrics, alarm configuration, compute resources, Git configuration, and permissions.
Overview
The workflow configuration panel displays the following items from top to bottom by default:
Area | Description |
Basic Information | Workflow ID, creator, run account, and description |
Scheduler Configuration | |
Parameter | |
Tags | Workflow tag management |
Monitoring metrics | Add monitoring metrics. |
Alarm Configuration | |
Computing Resource | Summary of computing resources associated with tasks in the workflow, with support for batch switching. |
Git Configuration | Git repository configuration |
Permission | Workflow-level ACL: Manage / Run / View / None |
Prerequisites
You are already the workflow owner or have Manage permission.
To modify sensitive configurations such as the running account and permissions, you must have the corresponding permission points.
Operation Steps
Step 1: Basic Information
Parameter | Description | Required | Default Value |
Workflow ID. | System-generated, unique identifier, copy supported. | - | Generated by the system |
Creator. | User who created the workflow. | - | Current User |
Run As account | Identity used during workflow execution. | Yes | Creator. |
Description | Workflow description, up to 10,000 characters. | No | Null |
Modify the running account:
1. Click the edit icon in the Running Account row.
2. Search for the target user in the drop-down list. Fuzzy matching by name or email is supported.
3. Click Save.
Note:
After you switch the running account, the workflow runs as the new account, and resource access permissions change accordingly. Make sure that the new account has the permissions required to run all files, data sources, and compute resources referenced by the tasks.
Step 2: Tags
Tags are used for multi-dimensional classification management of workflows, for example, organizing workflows by business domain, lifecycle, and owner.
Add tags
1. Click Add Tag in the Tag row. A tag management dialog box appears.
2. Click + Add to add a row:
Tag Name: Required. It can contain letters in all languages, uppercase and lowercase letters, digits, _, and -, with a maximum length of 128 characters.
Tag Value: Optional. The rules are the same as those for the tag name.
1. Click Confirm to save.
Tag Rules
Rule | Description |
Unique | Tag names must be unique within the same workflow. |
Upper Limit | A single workflow can contain up to 1,000 tags. |
Step 3: Monitoring Metrics
Click Add Metric to configure monitoring metrics for the workflow. These metrics are used for alarm evaluation or Ops dashboard display.
Step 4: Alarm Configuration
Detailed rules for workflow-level alarm configuration are provided in Alarms for Workflows and Tasks. This section describes only the entry points and differences. Item | Description |
Entries | Workflow configuration drawer > Alarm configuration > Add now. |
Monitoring Scenario | Start / Success / Failure / Monitoring metrics (run duration, wait duration, completion time) |
Receiving Channel | Email / Webhook / Teams / Slack |
Do Not Disturb | Do Not Disturb upon manual termination (only supported at the workflow level) |
Workflow alarms and task alarms are independent of each other and do not interfere with each other.
Step 5: Compute Resources
Compute resources for a workflow cannot be configured separately. They are aggregated from the resources associated with all tasks under the workflow:
No tasks created: The compute resource row displays Not configured.
Created tasks: Lists deduplicated compute resources, including status points, names, quotas, and available quotas.
Switching Compute Resources in Batches
1. Click Switch at the end of a resource row.
2. Select a new compute resource.
3. The system displays a dialog box indicating that the compute resources of N tasks will be modified in batches, and shows the list of affected tasks.
4. Click Update to complete the switch.
Step 6: Git Configuration
Click Add Configuration to associate a Git repository with the workflow for version management and collaborative development.
Step 7: Permissions
Workflows support four types of permissions:
Permission | View. | Copying | Running | Editing an alarm policy | Deleting an alarm policy | Permission Settings |
No permission | Not supported | Not supported | Not supported | Not supported | Not supported | Not supported |
View Permissions | Supported | Supported | Not supported. | Not supported. | Not supported. | Not supported. |
Running permission | Supported | Supported | Supported | Not supported | Not supported | Not supported |
Administrator permissions | Supported | Supported | Supported | Supported | Supported | Supported |
Configuring Permissions
1. Click Manage Permissions in the Permissions row to open the permission management dialog box.
2. The authorized list displays the permissions of all users and user groups.
3. Click Add Authorization:
Principal: Select a single user or user group. Search supports fuzzy matching by name or email.
Permission: Select View, Run, or Manage.
1. Click Confirm.
Permission Rules
The workflow creator has the Manage permission by default.
Workspace administrators have the Manage permission on all workflows by default and cannot be deleted.
Users with the Manage permission can set all four types of permissions for other members.
Parameter Description
Run As and ACL Integration
During task execution, the system uses the Run As account to verify ACL permissions for files, data sources, and compute resources. For detailed rules, see Members and Permission Management: Workflow ACL: See Step 7: Permissions in this document.
If the Run As account lacks any permission during task execution, the task is immediately set to failed, and the error message is recorded in the run log.
Use Limits
Workflow names must be unique within a workspace. Creating an API with a duplicate name is blocked by the backend.
Permission configurations are not carried over when a workflow is copied. You need to grant permissions again after the copy.
Deleting a schedule requires the Manage permission. Modifying the running account is subject to the Run As editable permission.
The Compute Resource configuration only displays a deduplicated list and does not carry independent resource options.
FAQs
Q1: If a user is granted the Run permission on a workflow, can they see it in the Workflow list?
Yes. Users with no permissions cannot see the workflow in the list, while users with the View, Run, or Manage permission can see it.
References