Actions22
- Cloud Extraction Actions
- Data Actions
- Task Actions
- Task Group Actions
Cloud Extraction → Start Subtasks
AI-generatedOverview
This node operation allows users to start specific subtasks within a cloud extraction task in Octoparse. It is useful in scenarios where a user wants to control the execution of individual subtasks rather than the entire task, enabling more granular management of data extraction processes. For example, a user can select a task group, then a task within that group, and finally choose which subtasks to start, allowing for targeted data extraction workflows.
Use Case Examples
- Starting specific subtasks in a cloud extraction task to resume or trigger partial data extraction without restarting the entire task.
- Managing subtasks individually to optimize resource usage and control extraction timing.
Properties
| Name | Meaning |
|---|---|
| Task Group | Select the task group to find the task in. This is required to scope the task selection within a specific group. |
| Task | Select the specific task within the chosen task group to operate on. |
| Subtasks | Select one or more subtasks within the chosen task to start. This allows starting only selected parts of the task. |
Output
JSON
subTaskId- Identifier of the subtask that was started.status- Current status of the subtask after the start operation.
Dependencies
- Requires an API key credential for Octoparse API authentication.
Troubleshooting
- Ensure the selected task group, task, and subtasks exist and are correctly loaded via the dynamic options methods.
- Common errors may include authentication failures if the API key is invalid or missing.
- Errors can also occur if the subtasks are already running or if the task IDs are incorrect.