Overview
Ops monitoring for offline synchronization tasks is organized around the following workflow: Task List → Version Management → Publishing → Permission Authorization → Running Instance Viewing. This document describes the entry points and procedures for various Ops operations, helping you view task status, roll back versions, control publishing pace, and diagnose runtime issues in daily use.
Tip
The actual running instances of offline sync tasks are generated through Workflow scheduling. Running details and logs can be viewed in the instance view of the Workflow task node. Entries
Entries | Path |
Task list | Data Integration > Ingestion task > Offline |
Task editing page | Click Edit in the Operation column on the task list page, or click the task name. |
Task Instance (Run Details) | Workflow > Workflow details > Task node |
Task List
The task list displays all offline sync tasks that the current user has permission to access.
Default Display Fields
Task name (click to go to the edit page).
Publish version.
Creator.
Last modified by.
Last modification time.
Complete Optional Fields
You can customize the displayed fields by clicking the settings icon on the right side of the list header to open the field selection dialog. The complete list of fields is shown in the following table:
Field | Description |
Task Name | Single-table synchronization task name |
Task ID | Unique task ID |
Published Version | Currently published version number |
Release time. | Last published time |
Creator. | Creator username |
Creation Time | Task creation time. |
Owner | Actual task running identity |
Last Modified By | User who last saved the task |
Last modification time. | Last saved time |
Tip
The customized display field settings are saved locally in the browser and remain effective the next time you access the page.
List Operations
Operation | Description |
Publish | Trigger task release check |
Editing an alarm policy | Go to the task editing page. |
Permission | |
Deleting an alarm policy | Delete Task (Irreversible) |
Batch Operations
The task list supports batch publishing after multiple selection:
1. Select one or more tasks.
2. Click Batch Publish, and a publish check dialog will pop up.
3. Switch to view the check results of each task.
4. Select Recheck / Continue Publishing / Ignore Exceptions and Publish.
Version Management
Historical Versions
Each time a user clicks Save, a historical version is generated. A maximum of 200 versions are retained. If this limit is exceeded, the earliest unpublished versions are automatically deleted.
Go to the task editing page and click the Version Management icon in the upper-right corner to view the version list:
Field | Description |
Version name | Consists of the save time in the format "month day hour minute second". |
Creator. | User who saved |
Label | Published version displays "Published". |
Creating a Version
Operation | Action |
Save | Generate a new historical version; prompt "Task saved successfully"/"Task save failed: ${failure reason}". |
Save Only | Same as above. |
Create and Publish / Save and Publish | Same as above. |
Deleting a Version
Operation options:
Operation | Description |
Delete a single version | Hover over a historical version and click Delete to remove it. At least one version must be retained. |
Clear | After confirmation, clear all versions (retain the released version and the latest version). |
Warning
Delete Published Version triggers an additional confirmation: "You are deleting a published version. This operation may cause exceptions in modules associated with this task." If you continue, the task publishing status changes to Unpublished, and workflows that reference this task will fail with the message "Task not published."
Version Rollback
Version rollback is the process of copying a version, editing it, and publishing it:
1. Click a version in the historical version list to return to that version. The editing page then switches to the configuration of that version, and a temporary editing version is generated based on it.
2. Click Save to generate the latest saved version.
3. Click Publish to save and publish, generate a new version, and point the published version to that version.
Release Process
Single-Table Task Publishing
Entry: Click Publish in the operation area of the task list or task editing page.
Publishing process:
Click Publish to open the publish check dialog.
├─ All passed: Select "Recheck" or "Continue to Publish".
└─ Partial exceptions: Select "Recheck" or "Ignore Exceptions and Publish".
Phase | Check Item |
Task Saving | Serialization and Persistence |
Configuration Check | Source / Target / Mapping |
Data Source Check | Source/Target Connectivity, Source Permissions |
Resource Check | Resource Status |
Publish completion message:
Success: The message "Task published successfully" is displayed.
Failure: The message "Task publishing failed: ${failure reason}" is displayed.
Publishing version rules:
The publish operation sets the current edited version as the published version.
A task retains only one published version: A subsequent publish replaces the old published version with the new version.
The "Published" indicator in the list moves with the current published version.
Batch Task Publishing
After selecting multiple tasks in the task list, click Batch Publish:
1. A publish check dialog pops up, displaying the check status of each task in the list.
2. You can view by status: Passed, Abnormal, In Progress.
3. The progress bar displays the number of passed and abnormal items.
4. Select Recheck / Continue Publishing / Ignore Exceptions and Publish.
Permission Management
Permission Items
Permission | Operation scope |
Manageable | View / Edit / Run / Delete / Grant permissions |
Runnable | View / Edit / Run |
Editable | View / Edit |
Viewable | You can only view items. |
Tip
The Runnable permission also controls debug runs: Only users with the Runnable permission or higher can debug tasks.
Default Permissions
Workspace administrators have the Manage permission by default, and this permission cannot be revoked.
Task owners have all permissions by default, and these permissions cannot be revoked.
Operation Entry
Entries | Path |
Task list | In the operation column, choose More > Permissions |
Viewing Running Instances
Tip
Offline sync tasks are triggered to run through Workflow. The entry for viewing task instances is: Workflow > Workflow Details > Task Node. Data overview
The instance run details provide the following metrics:
Type | Field |
Read | Read Size, Record Quantity |
Write | Write Size, Number of Records |
Test Duration | Execution Duration, Speed, Dirty Data |
Reading Node Details
Field | Description |
Data source. | Database.table
|
The total number of entries | Total records read |
Total bytes | Total bytes read |
Speed | Rows/s |
Throughput | Bytes/s |
Waiting time for read | Blocked waiting time |
Number of dirty data records | Number of dirty data records that failed to parse or exceeded the threshold |
Writing Node Details
The fields are the same as those for the read node, but the described object is the target table: Target Table, Total Records, Total Bytes, Speed, Throughput, Read Wait Time, and Dirty Data Records.
Instance Operations
The following operations are supported in the workflow task instance details:
Operation | Trigger Conditions |
Running | The instance has not started. |
Terminate | The instance is running. Stop the instance after secondary confirmation. |
Retry | The instance has failed. |
Run Logs
The entry is the same as that for run instances: In the Workflow task instance details, switch to the Run Log tab.
Function | Description |
Switch Logs | Multiple executions of an instance (for example, retries) generate multiple log records. The records are named with the start and end time, and can be viewed one by one. |
Log Content | Display complete running logs in text format |
Download | Click Download in the upper-right corner to export the logs as a .log file. |
Deleting a Task
Entries
Entries | Path |
Task list | In the operation column, choose More > Delete |
Prerequisites for Deletion
The current account has the Manage permission on the task or is the task owner.
Deletion Behavior
1. After Delete is clicked, a confirmation dialog appears.
2. After confirmation, the task is deleted (actually a soft delete, which facilitates exception recovery).
3. Assets already completed through this task (such as synced data and created target tables) are not affected.
4. When an entity that references this task (such as a workflow) is executed, the error "Task deleted" is reported.
5. Deletion operations are recorded in CloudAudit logs (to be supplemented) for traceability.
FAQs
Q: Why Can't I See the Task I Created in the List?
A: Check the following:
1. Whether the currently selected Workspace is the Workspace where the task was created.
2. Whether the filter conditions (such as creator and last modified time) limit the display range.
3. Does your account have the View permission on this task? For details, see Members and Management Permissions.
Q: When Will Scheduled Workflows Use the New Version After a Version Is Released?
A: The latest published version is used in the next workflow scheduling. Running instances do not switch to the new version.
Q: Can a Task Be Recovered After Deletion?
A: The platform uses soft deletion to facilitate exception recovery, but does not provide an external recovery entry. To restore data, submit a ticket to contact technical support.
Q: If Some Tasks Fail During a Batch Release, Will Other Tasks Be Affected?
A: No impact. Each task is detected and published independently. In the progress dialog, you can click Re-detect or Ignore Exception and Publish for failed tasks.
Q: How to Quickly Identify the Cause of an Instance Failure?
A: In the Workflow task instance details:
1. In Data Overview, check whether the "Dirty Data Volume" exceeds the threshold.
2. Switch to the Run Log tab to view detailed errors.
3. Click Download Logs to export the .log file for further analysis or feedback to technical support.
References