@clickzetta/cz-cli-darwin-arm64 0.3.95 → 0.3.100

package/bin/skills/lakehouse-doc-en/references/task-develop.md

@@ -0,0 +1,277 @@
+# Task Development and Scheduling Configuration
+
+## Overview
+
+"Development" refers to the big data integrated development environment (IDE), providing developers with an efficient, intelligent online working environment. It supports users in task writing, debugging, scheduling configuration, submission and publishing, completing the key processes of big data processing and analysis.
+
+Click "Development" in the left navigation menu to enter the main interface.
+
+## Interface Overview
+
+![](.topwrite/assets/image_1735640592511.png)
+
+| No. | Function                                                        |
+| -- | --------------------------------------------------------- |
+| 1  | Function switch                                                      |
+| 2  | Switch workspace: This section displays the name of the current data development project space and the region you are in. You can click the dropdown icon to switch to other project spaces. |
+| 3  | Development directory tree: The directory tree is used to manage task code in an orderly manner. You can create directory trees according to business needs to manage tasks by category and hierarchy.        |
+| 4  | SQL editing area: The main operation interface for development. Different types of editing areas have different operation interfaces.                         |
+| 5  | Run results: Presents the results after running operations in the SQL editing area.                            |
+
+## Directory Tree
+
+The data development module displays all tasks under the current project in a directory tree format, making it easy to add, delete, modify, and query tasks.
+
+Supported operations on the directory tree:
+
+* **Switch tab**: Switch the type of directory tree below by clicking the tab, i.e., task directory tree or data directory tree.
+
+* **Task directory tree**: Displays all tasks in the current space.
+
+* **Data directory tree**: Displays all data directory trees in the user's region, presented in the workspace-schema-table/view hierarchy.
+
+* **Create**: Create folders and various development tasks by clicking the + button on the directory tree.
+
+* **Development task types**: Real-time sync, offline sync, SQL script, Python script, shell script
+
+* **Filter tasks**: Supports filtering tasks by development task type, submission status, and responsible person.
+
+* **Refresh**: Refresh the current directory tree information.
+
+* **Search tasks**: Search and locate specific tasks by task name or path.
+
+* **Task name**: Fuzzy match keywords with "task name" to return matching file directories or tasks.
+
+* **Path**: Fuzzy match keywords with the task's path to return matching file directories or tasks.
+
+* **Create subdirectory & create subtask**: When hovering over a subdirectory, more icons appear. Click to perform the following operations:
+
+* **Current directory is a folder**: Create any task type, new folder, delete, rename at the current level.
+
+* **Current directory is a task**: Open task, create copy, copy name, rename, move, delete at the current level.
+
+**Operation notes**:
+
+* Create copy: Copy the current task, including its scheduling configuration.
+* Copy name: Copy the current directory name.
+* Rename: Rename the directory name.
+* Move: Move the directory to another directory within the project. If the directory contains subdirectories or tasks, they will be moved together.
+* Delete: Delete the directory.
+* **Task directory tree**: Icons distinguish task types, and colors distinguish online status.
+
+![](.topwrite/assets/43961fb877/97e53c195a68bc32dc20f8d05406a65814f50ebf.png =283)
+
+| Status Legend                                                                              | Description                       |
+| --------------------------------------------------------------------------------- | ------------------------ |
+| ![](.topwrite/assets/43961fb877/cf868103bc526077f03e907734acc40282147b16.png =54) | After task submission, the saved version differs from the submitted version.   |
+| ![](.topwrite/assets/43961fb877/c09176dc520bc8b67fd0332486a742f98c996e4c.png =52) | After task submission, the server-side saved version matches the submitted version. |
+| ![](.topwrite/assets/43961fb877/3c8f88221d1cb5096a50fe2f871717264c355624.png =50) | After task submission, click the offline operation.            |
+| ![](.topwrite/assets/43961fb877/4ffcc5e1d5ceda6d460b753cce8e713d4cd1eb58.png =45) | Other status types.                  |
+
+| Icon Legend                                                                              | Description       |
+| --------------------------------------------------------------------------------- | -------- |
+| ![](.topwrite/assets/43961fb877/c09176dc520bc8b67fd0332486a742f98c996e4c.png =45) | Real-time sync     |
+| ![](.topwrite/assets/43961fb877/c7a4258cc7c3fffb428b3393d189d5b56d1352b8.png =40) | Offline sync     |
+| ![](.topwrite/assets/43961fb877/b0a4f31a60e860ec4168f2a6aa6c75bd349882ff.png =46) | SQL script    |
+| ![](.topwrite/assets/43961fb877/a34b52a1a518262075162653a0e7bd5efdf8373d.png =43) | Shell script  |
+| ![](.topwrite/assets/43961fb877/9a58c3506c9ddc8c176f67d1224b55de6a08ebb0.png =40) | Python script |
+
+## Task Development Process
+
+The data development module leverages Lakehouse's underlying engine capabilities to provide multiple development types. Users can choose the task type for interactive data development work.
+
+### Create a New Task
+
+Currently, two types of task nodes are supported: data integration and data development.
+
+Click "New" and select the specific development type. A popup will appear. Enter the task name, select the specific directory level where the task should be saved, and then enter the development interface.
+
+![](.topwrite/assets/image_1690523560494.png =210)
+
+### Operation Bar Description
+
+#### Task Tab
+
+![](.topwrite/assets/43961fb877/904d8da4a2bade280ba2901837430ed51d2f5fdd.png)
+
+After clicking the task directory tree on the left or creating a new task node, the task tab will open (or be brought into focus). In the task tab bar, users can perform the following operations:
+
+**New**: Click the "+" button in the tab status bar to quickly create a new task, which is saved by default under the root node of the current space.
+
+**Close tab**: Hover over a tab, and a downward button will appear, allowing batch closing of task tabs.
+
+Tab color status mapping:
+
+| Status Icon | Description   |
+| ---- | ---- |
+| Green   | Run successful |
+| Red   | Run failed |
+| Blue   | Running |
+| Gray   | No run |
+
+#### SQL Function Area
+
+![](.topwrite/assets/43961fb877/d87ab875a66382a674db74e3afeeeb3b722100d6.png)
+
+| No. | Function Name   | Description                                                                                                     |
+| -- | ------ | ------------------------------------------------------------------------------------------------------ |
+| 1  | Save     | Save the task, including the current node code and related configurations.                                                                               |
+| 2  | Format    | Format the written code to make the syntax structure look clean and concise.                                                                                 |
+| 3  | Parameters     | Not yet online.                                                                                                  |
+| 4  | Versions     | Click Versions to view the submitted and saved versions of the current task. Supports code viewing and code rollback between versions.                                                             |
+| 5  | Scheduling     | Click to open a sidebar panel for scheduling configuration. See Scheduling Settings for details.                                                                          |
+| 6  | Submit     | The "Submit" function is only needed for tasks that require scheduled dispatch. After "Submit", the task is published to the Operations Center and runs according to the configured schedule. Before submission, scheduling configuration is required. See Scheduling Settings for details.                  |
+| 7  | Operations     | Click to enter the "Operations" center.                                                                                             |
+| 8  | Task flow tips | Hover over the task flow tips to display the online flowchart for the development task.                                                                       |
+| 9  | Cluster filter   | The "default" shown in the figure indicates the Virtual Cluster used for task execution. Click to switch to another Virtual Cluster. To add a new Virtual Cluster, go to "Compute". |
+| 10 | Run/Stop  | Run/Stop the current node's code. When running SQL code, you can select and run a portion of the code.                                                                   |
+
+#### SQL Editing Area
+
+![](.topwrite/assets/43961fb877/daf1fe91a75052ac12b25b198449827de8d56ff5.png)
+
+* Schema switching: Click the dropdown to switch schemas in the current workspace. The default is "public".
+* Shortcuts: Various capabilities supported in the Studio development editing area. See Others: Common Shortcut Operations for details.
+* SQL editing area: The SQL editor in Studio provides the following features to improve data development and analysis efficiency.
+
+| Feature       | Description                                        |
+| -------- | ------------------------------------------- |
+| Code folding     | Collapse code blocks to reduce reading distractions.                             |
+| Real-time syntax error prompts | Prompt users of syntax errors found during code writing to help avoid mistakes.             |
+| Syntax highlighting     | Use different colors or fonts to highlight keywords and syntax structures in the editor or IDE to enhance readability. |
+| Intelligent completion     | Automatically complete keywords, function names, variable names, etc., in code based on context and known information to improve coding efficiency and precision.   |
+| Partial code execution   | Run only a portion of the code instead of the entire program for quick testing of small code segments or debugging.             |
+
+### Scheduling Settings
+
+After the task has been tested and everything works correctly, if you want to run the task on a scheduled basis, you need to configure the task's scheduling properties. Click the "Scheduling" button in the SQL function area.
+
+#### Basic Information
+
+| Parameter     | Description                                                                                                                                         |
+| ------ | ------------------------------------------------------------------------------------------------------------------------------------------ |
+| Owner    | Required. Only one member allowed, defaults to the task creator. Can be changed to another workspace member as needed.                                                                                                  |
+| Description     | Optional. Provides a detailed description of the task for future reference and management.                                                                                                                  |
+| Run attributes   | Required. Normal scheduling: Runs according to the user's scheduling rules. Dry-run scheduling: When a task's logic does not need to run temporarily but you don't want to disrupt the data pipeline, set it to dry-run; the task will be marked as successful. Paused: After setting the task to "Paused" and publishing to the Operations Center, the task status is "Paused" and no task instances are generated, but backfill operations are still possible. |
+| Cluster     | Required. Defines the scheduling resource group used when the task is published to production.                                                                                                            |
+| Schema | Required. Defines the prefix schema used when the task runs in production.                                                                                                            |
+| Task priority  | Optional. Sets the scheduling priority for Lakehouse SQL tasks, supporting 10 levels (0-9), where higher numbers mean higher priority.                                                                                          |
+| Parameter configuration   | Click "Add Parameter" to add a new parameter. Click "Load Parameters in Code" to automatically load parameters already used in the code. In code, parameters are referenced as: '${bizdate}'. Note: more system built-in parameters will be supported in future versions.                                |
+
+#### Scheduling Time
+
+![](.topwrite/assets/image_1756191463019.png =379)
+
+| Parameter       | Description                                                                                |
+| -------- | --------------------------------------------------------------------------------- |
+| Scheduling cycle     | Daily: Runs every day. Monthly specified day: User selects specific days each month. Weekly specified day: User selects specific days each week.           |
+| Scheduling frequency     | Execute once: Only the start scheduling time needs to be configured. Execute multiple times: Also requires scheduling interval, start time, end time, and exclusion time settings. |
+| Scheduling interval | When executing multiple times, users can customize the interval between each execution, from 1 minute to 12 hours.                                     |
+| Start scheduling time   | The time when daily instances begin executing.                                                                       |
+| End scheduling time   | The time when daily instances stop executing.                                                                       |
+| Exclusion time settings   | No instances will be generated during the specified exclusion time ranges.                                              |
+| Effective time     | The date from which the task takes effect.                                                                        |
+| Expiry time     | The date from which the task expires.                                                                        |
+| Preview scheduling time   | Click to preview the actual run times after configuration.                                                         |
+
+#### Instance Information
+
+Studio supports two instance generation modes: **Effective next day** and **Effective after publishing**.
+
+| Parameter         | Description                                                                                                          |
+| ---------- | ----------------------------------------------------------------------------------------------------------- |
+| Instance generation mode     | Effective after publishing: Instances are generated immediately after publishing and run according to the configured schedule. Effective next day: Instances run on the following day.                                               |
+| Instance retry on error     | Defines whether a task instance can be retried, considering data idempotency. Set as needed. Can retry after success or failure. Cannot retry after success, can retry after failure. Cannot retry after success or failure.                        |
+| Auto retry count     | Custom number of retries.                                                                                                     |
+| Instance timeout duration     | Not enabled / Custom. If a task instance runs longer than the set duration, it will be marked as failed. Changes only apply to new instances after the task is submitted.                                           |
+| Preview scheduling time     | Click to preview the actual run times after configuration.                                                                                   |
+| Parameter configuration       | Click "Add Parameter" to add a new parameter. Click "Load Parameters in Code" to automatically load parameters already used in the code. In code, parameters are referenced as: '${bizdate}'. Note: More system built-in parameters will be supported in future versions. |
+| Scheduling wait duration     | If a task instance reaches its scheduled time and waits longer than this setting (still waiting for upstream tasks to finish), the system will mark it as failed to prevent scheduling backlogs.              |
+| Delayed run skip duration | Based on the difference between the task instance's actual start time and the configured scheduled time. If the difference exceeds this setting, the instance is skipped as a dry run and marked as successful.                                        |
+
+#### Scheduling Dependencies
+
+Complex production tasks typically have upstream and downstream dependencies. For example, DWD processing tasks depend on ODS layer tasks. In "Scheduling Dependencies", you can add upstream tasks that the current task depends on. Two methods are supported: parent node's file name, and table name produced by the parent node.
+
+Dependency strategy: Currently supports default strategy, forward dependency, and forward nearest dependency. For specific instance generation methods for each strategy, see [Task Scheduling Dependencies](task_scheduling_dependency.md).
+
+![](.topwrite/assets/image_1756191826292.png =660)
+
+#### Task Output
+
+There are two ways to configure task output information:
+
+Method 1: Automatically generate output table names through code auto-parsing mentioned above.
+
+Method 2: Manually add by searching table names.
+
+![](.topwrite/assets/image_1690523641208.png =437)
+
+For more information about task scheduling, refer to: [Task Scheduling Dependencies](task_scheduling_dependency.md), [Task Scheduling and Instance Execution](f6fc6447ee.md).
+
+### Submit for Publishing
+
+Click the **Submit for Publishing** button in the editor's toolbar to submit the task.
+
+### Operations View
+
+Click to jump to the "Operations" center to view task operations.
+
+## Run Results
+
+### Run History
+
+Run history provides up to 20 recent run result records for the current task tab within 7 days.
+
+![](.topwrite/assets/43961fb877/5356056744906f50b383683a6665b649efc6178d.png)
+
+### Run Results
+
+#### Logs
+
+SQL jobs can be diagnosed based on logs. For details, see [JOB PROFILE](web-job-history.md).
+After clicking to run the task, you can view detailed log information in the log area at the bottom of the page.
+
+Use the expand and collapse buttons to adjust the log display area.
+
+Use the refresh button to force refresh the logs.
+
+![](.topwrite/assets/43961fb877/e3e8ee2c80e29d7dc8bcc52df9c14e68564c9cc3.png)
+
+#### Data
+
+After the task completes, results (such as from SELECT statements) are displayed in the "Data" tab:
+
+![](.topwrite/assets/43961fb877/2b76b47e9714fd6d8ae4276a935f173a971296e1.png)
+
+## Others: Common Shortcut Operations
+
+The following shortcuts are supported in the code editor to improve editing efficiency:
+
+* **Save**
+  * MAC: CMD + s
+  * Windows: Ctrl + s
+* **Comment/Uncomment the current line or code block**
+  * MAC: CMD + /
+  * Windows: Ctrl + /
+* **Cut the current line or code block**
+  * MAC: CMD + x
+  * Windows: Ctrl + x
+* **Copy the current line or code block**
+  * MAC: CMD + c
+  * Windows: Ctrl + c
+* **Paste**
+  * MAC: CMD + v
+  * Windows: Ctrl + v
+* **Batch line operations**
+  * Mac: Shift + Option
+  * Windows: Hold Shift + Alt
+
+## Related Documents
+
+- [Task Parameters](task_param.md) — Use dynamic parameters (dates, timestamps, etc.) in SQL tasks
+- [Task Parameter Syntax Reference](task_param_reference.md) — Complete syntax for system built-in parameters, time expressions, and time functions
+- [Task Parameter Scenario Examples](task_param_examples.md) — Complete business scenarios such as daily, monthly, and weekly reports
+- [Workflow (Composite Task)](composite_task.md) — Orchestrate multiple SQL tasks into a DAG
+- [Task Groups](task_group.md) — Share parameters across tasks and manage them uniformly
+- [Python Tasks](python-task.md) — Use parameters in Python scripts

package/bin/skills/lakehouse-doc-en/references/task-instance-maintenance.md

@@ -0,0 +1,198 @@
+# Task and Instance Operations
+
+The Operations Center provides management operations for tasks and instances. The tasks managed by the Operations Center include manually triggered tasks and periodically scheduled tasks, along with their corresponding instances, for centralized management.
+
+* Task: A file created in the IDE and submitted to the Operations Center is called a task.
+* Instance: A specific running entity generated by manually executing a file or by scheduled tasks is called an instance.
+
+## Task Operations
+
+### Task List
+
+Click "Task Operations" in the left navigation to enter the task list page. The task list provides a summary display of tasks in all workspaces under the currently enabled service.
+
+![](.topwrite/assets/image_1740376826829.png)
+
+#### Task List Content
+
+In the list, you can view key attributes such as task name, task ID, workspace, task status, and task type.
+
+#### Task List Operations
+
+In the task list, you can select single or multiple tasks for quick operations.
+
+**Single Task Operations**
+
+| Operation Name | Operation Description                                                                                                                                                                               |
+| -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Pause          | Can only be operated on tasks that are not paused. After the operation, the task's scheduling attribute will be set to "Pause Scheduling," meaning no more task instances will be generated or run. |
+| Start          | Can only be operated on paused tasks. After the operation, the task's scheduling attribute will be restored to "Normal Scheduling," meaning task instances will be generated and run.               |
+| Delete         | Removes the task from the Operations Center, reverting the task to the "Unsubmitted" state in the file.                                                                                             |
+
+**Batch Operations for Multiple Tasks**
+
+| Operation Name | Operation Description                                                                                |
+| -------------- | ---------------------------------------------------------------------------------------------------- |
+| Batch Start    | Batch operation on selected tasks, restoring the task's scheduling attribute to "Normal Scheduling." |
+| Batch Pause    | Batch operation on selected tasks, setting the task's scheduling attribute to "Pause Scheduling."    |
+
+#### Task List Filtering
+
+At the top of the task list, you can filter tasks based on their attributes as needed.
+
+| Operation Name | Operation Description                                   |
+| -------------- | ------------------------------------------------------- |
+| More Filters   | Click to expand more filter conditions.                 |
+| Reset Filters  | Click to reset and clear all current filter conditions. |
+| Refresh        | Refresh the list based on the given filter conditions.  |
+
+#### Task Details
+
+From the task list, click the task name link to enter the task details page. On this page, you can view basic information, upstream and downstream dependency graphs, task instances, and code.
+
+**Basic Information**
+
+In this area, you can view the basic information of the task. You can collapse or expand it as needed.
+
+^
+
+**Dependency Graph**
+
+In the dependency graph, you can view the directly upstream tasks that the current task depends on and the directly downstream tasks that depend on it.
+
+![](.topwrite/assets/image_1740376848273.png =640)
+
+| Operation Name | Operation Description                                                                                                     |
+| -------------- | ------------------------------------------------------------------------------------------------------------------------- |
+| Search         | Quickly locate the task node on the graph by given task name or task ID keywords. The matching method used is "contains." |
+| Refresh        | Click to reload the entire dependency graph.                                                                              |
+
+^
+
+**Task Instances**
+
+In the task instance area, all task instances generated by the current task for all time ranges will be displayed.
+
+![](.topwrite/assets/image_1740376863239.png)
+
+For a single task instance, basic control operations can be performed:
+
+| Operation Name | Operation Description                                                                                          |
+| -------------- | -------------------------------------------------------------------------------------------------------------- |
+| Stop           | Can be operated to stop instances that are not running.                                                        |
+| Rerun          | Can be operated to rerun instances that have reached a terminal state, meaning the instance will be run again. |
+
+**Code**
+
+The node code area displays the latest version of the code for the current task.
+
+![](.topwrite/assets/image_1740376885507.png)
+
+**Task Operations**
+
+On the task details page, you can pause, start, or delete the task, with the same meaning and effect as the operations provided in the list.
+
+| Operation Name | Operation Description                                                                                                                                                                                               |
+| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Pause          | Can only be operated on tasks that are not in a paused state. After the operation, the scheduling attribute of the task will be set to "Pause Scheduling", meaning no more task instances will be generated or run. |
+| Start          | Can only be operated on tasks that are in a paused state. After the operation, the scheduling attribute of the task will be restored to "Normal Scheduling", meaning task instances will be generated and run.      |
+| Delete         | Operates to take the task offline from the maintenance center, returning the task to the "Not Submitted" state in the file.                                                                                         |
+
+## Instance Maintenance
+
+### Instance List
+
+Click "Instance Maintenance" in the left navigation to enter the instance list page. The instance list provides a summary display of task instances in all workspaces under the currently opened service instance.
+
+![](.topwrite/assets/image_1740376898794.png)
+
+^
+
+#### Instance List Content
+
+In the list, you can view key attributes such as instance ID, corresponding task name, instance type, workspace, instance status, scheduled time, execution time, and completion time.
+
+#### Instance List Filtering
+
+At the top of the instance list, you can filter based on the task attributes as needed.
+
+| Operation Name | Operation Description                                      |
+| -------------- | ---------------------------------------------------------- |
+| More Filters   | Click to expand more filter conditions                     |
+| Reset Filters  | Click to reset and clear all current filter conditions     |
+| Refresh        | Refresh to retrieve the list based on the given conditions |
+
+#### Instance List Operations
+
+In the instance list, you can select one or more task instances for quick maintenance operations.
+
+![](.topwrite/assets/image_1740376909896.png)
+
+^
+
+#### Single Task Instance Operations
+
+| Operation Name | Operation Description                                                                                                                                                                                                                                                                                                                                                     |
+| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Pause          | Can only be operated on task instances that are not in a paused state. After the operation, the scheduling attribute of the task instance will be set to "Pause Scheduling", meaning the task instance will no longer be scheduled to run.                                                                                                                                |
+| Resume         | Can only be operated on task instances that are in a paused state. After the operation, the scheduling attribute of the task instance will be restored to "Normal Scheduling", meaning the task instance will run according to the set schedule time.                                                                                                                     |
+| Terminate      | Can only be operated on running task instances. After the operation, the task instance will be terminated, and the task instance status will be set to failed.                                                                                                                                                                                                            |
+| Rerun          | Can only be operated on completed task instances. After the operation, the task instance will be rerun.                                                                                                                                                                                                                                                                   |
+| Set Success    | Can only be operated on failed task instances. After the operation, the task instance will be forcibly set to success. This can be used in emergency maintenance scenarios where it is determined that even if the current task instance fails, it will not affect the correctness of downstream task data, thus removing the blockage for downstream task instance runs. |
+| Set Failure    | Can only be operated on successful task instances. After the operation, the task instance will be forcibly set to failed.                                                                                                                                                                                                                                                 |
+
+#### Batch Task Instance Operations
+
+| Operation Name | Operation Description                                                                                         |
+| -------------- | ------------------------------------------------------------------------------------------------------------- |
+| Pause          | Same as single operation. Note that it can only be operated on task instances that are not in a paused state. |
+| Resume         | Same as single operation. Note that it can only be operated on task instances that are in a paused state.     |
+| Terminate      | Same as single operation. Note that it can only be operated on running task instances.                        |
+| Rerun          | Same as single operation. Note that it can only be operated on completed task instances.                      |
+| Set Success    | Same as single operation. Note that it can only be operated on failed task instances.                         |
+| Set Failure    | Same as single operation. Note that it can only be operated on successful task instances.                     |
+
+### Instance Details
+
+From the instance list, click the instance ID link to enter the details page of the task instance. On this page, you can view basic information, upstream and downstream dependency graphs, task instances, and code.
+
+#### Basic Information
+
+In this area, you can view the basic information of the task instance.
+
+![](.topwrite/assets/image_1740376922155.png)
+
+#### Dependency Graph
+
+In the dependency graph, you can view the direct upstream task instances that the current task instance depends on, to quickly determine whether the current task instance can be scheduled normally.
+
+![](.topwrite/assets/image_1740376933802.png =640)
+
+##### Dependency Graph Operations
+
+| Operation Name | Operation Description                                                                                                                                       |
+| -------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Search         | By providing a keyword of the task name or instance ID, you can quickly locate the task instance node on the graph. The matching method used is "contains". |
+| Refresh        | Click to reload the entire dependency graph                                                                                                                 |
+
+In the DAG graph, you can switch to choose to directly tile or group nodes, for example, to aggregate instance nodes with the same status into one group.
+
+![](.topwrite/assets/image_1740376950665.png =640)
+
+#### Code
+
+The code area will display the version of the code used by the current task instance at runtime. Please note that this is the code used when the task instance was executed, which may not be the latest version of the task's code.
+
+#### Execution Logs
+
+The execution logs area will display all logs of the current instance execution, including logs generated after the task instance is rerun. Click the + icon on the left side of the list to expand and view detailed content.
+
+#### Operation Logs
+
+The operation logs area will display records of operations on the current instance.
+
+### Instance Operations
+
+On the task instance details page, you can pause, resume, terminate, rerun, or mark the task instance as successful. The meaning and function are the same as the operations provided in the list.
+
+![](.topwrite/assets/image_1740377018441.png)

package/bin/skills/lakehouse-doc-en/references/task_development.md

@@ -0,0 +1,54 @@
+# Task Development Overview
+
+The task development module is a visual development page provided by Singdata Lakehouse for developers. In this module, you can organize and orchestrate tasks, develop task logic, configure scheduling, run tests, and submit and publish tasks.
+
+## Development Concepts
+
+| **Concept** | **Definition** |
+| ------ | ----------------------------------------------------------------------------------------------------------------------------------------- |
+| Task | Simple node: a single, concrete task type, such as SQL or Python. |
+| | Complex workflow node: a group of nodes composed of multiple individual nodes, such as a composite node. Parameters and scheduling configuration for complex workflow nodes are managed centrally. |
+| Task Group | A task group is a virtual management concept provided by Singdata Lakehouse. You can add tasks to a task group for centralized management, including visual drag-and-drop dependency orchestration, task group parameter configuration, batch scheduling setup, and batch submission. **Note**: If you need to manage a group of tasks using a DAG-style drag interface, or copy and refactor a batch of task pipelines, the task group feature is recommended. |
+
+## Dependencies: Node-level Dependencies
+
+Dependencies are attached to nodes. Whether a node is a simple node or a complex workflow node, each acts as an independent dependency point.
+
+**Note**: Regardless of whether you create task nodes directly under "Tasks" or manage them within a task group, dependencies always exist at the task node level — that is, dependencies are between nodes. There is no concept of dependencies between task groups.
+
+^
+
+## Scenario Overview
+
+- You can create various task nodes directly under "Tasks" and establish dependencies between nodes through the scheduling dependency settings in the scheduling configuration.
+- You can also create new nodes or add existing nodes under a "Task Group" to organize and orchestrate a batch of tasks, including configuring task group-level parameters and visually dragging to set dependencies between tasks.
+
+| **Development approach** | **Target users** | **Scenario advantages** | **Limitations and differences** |
+| -------- | ---------------------- | ---------------------------------------- | --------------------------------------------------------------- |
+| Create tasks directly | Teams with relatively innovative business needs or those who prefer a fast, lightweight pace. | No need to build complex business relationships — just set up node dependencies and get the pipeline running quickly. Ideal for fast-moving scenarios. | Does not support batch operations, such as bulk modification of task scheduling times or compute clusters. |
+| Manage tasks within a task group | Mature, standardized data warehouse teams that organize work around business domains. | Manage a related batch of task nodes by business scenario, with support for visual drag-and-drop dependency configuration. | Real-time tasks are not currently supported in task groups. A task node can only belong to one task group. Task group parameters only take effect after the task group is submitted. |
+
+^
+
+### Glossary
+
+#### Task Group
+
+A task group is a virtual management concept provided by Singdata Lakehouse. You can add tasks to a task group for centralized management, including visual drag-and-drop dependency orchestration, task group parameter configuration, batch scheduling setup, and batch submission.
+
+- **Note**: If you need to manage a group of tasks using a DAG-style drag interface, or copy and refactor a batch of task pipelines, the task group feature is recommended. For more details, see [Task Group](task_group.md).
+
+#### Task
+
+Singdata Lakehouse provides several types of task nodes, including real-time multi-table sync, offline sync, real-time sync, SQL development, Python, Shell, virtual nodes, and more. Choose the appropriate task type based on your business needs.
+
+#### Parameters
+
+- **Task group parameters**: Parameters created within a task group, used for global management of tasks inside that group.
+- **Scheduling parameters**: Parameters used during scheduled task execution.
+- **Temporary parameters**: Parameters used during ad-hoc task execution.
+
+#### Scheduling Configuration
+
+- Currently, only periodic scheduling is supported.
+- **Dependency method**: Interval dependency — the system determines whether upstream and downstream task instances overlap by comparing their start and end time ranges. For more on dependency relationships, see [Task Scheduling Dependencies](task_scheduling_dependency.md).