Actions22
- Cloud Extraction Actions
- Data Actions
- Task Actions
- Task Group Actions
Cloud Extraction → Stop Subtasks
AI-generatedOverview
This node operation stops specific subtasks within a cloud extraction task in Octoparse. It is useful when you want to halt certain parts of a larger data extraction task without stopping the entire task. For example, if some subtasks are no longer needed or are causing issues, you can selectively stop them to optimize the extraction process.
Use Case Examples
- Stopping subtasks that are no longer required in a cloud extraction task to save resources.
- Halting subtasks that are malfunctioning or producing incorrect data without interrupting the entire extraction task.
Properties
| Name | Meaning |
|---|---|
| Task Group | Select the task group to find the task in, required to identify the context of the task. |
| Task | Select the specific task within the chosen task group to manage subtasks for. |
| Subtasks | Select one or more subtasks within the chosen task to stop. |
Output
JSON
subTaskId- Identifier of the subtask that was stoppedstatus- Status of the subtask after the stop operation
Dependencies
- Octoparse API with an API key credential for authentication
Troubleshooting
- Ensure the task group ID, task ID, and subtask IDs are correctly selected and valid; invalid IDs will cause API errors.
- If the API returns an error about permissions, verify that the API key has sufficient rights to stop subtasks.
- Network or authentication issues may cause request failures; check API credentials and connectivity.
Links
- Octoparse Cloud Extraction API - Stop Subtasks - Official documentation for stopping subtasks in Octoparse cloud extraction tasks.
