Actions22
- Cloud Extraction Actions
- Data Actions
- Task Actions
- Task Group Actions
Data → Mark Data as Exported
AI-generatedOverview
This node operation marks data associated with a specific task as exported in the Octoparse system. It is useful in workflows where you want to update the status of data after processing or exporting it, ensuring that the same data is not processed multiple times. For example, after extracting and exporting data from a web scraping task, you can use this operation to mark that data as exported to keep track of processed records.
Use Case Examples
- Mark data as exported for a given task to prevent reprocessing in subsequent workflow runs.
- Use after data extraction and export to update the data status in Octoparse.
Properties
| Name | Meaning |
|---|---|
| Task Group | Select the task group to find the task in. This is required to identify the context of the task whose data is being marked as exported. |
| Task | Select the specific task whose data you want to mark as exported. This is required to specify the exact data set to update. |
Output
JSON
data- The response data from the Octoparse API after marking the data as exported, typically confirming the operation's success or providing updated data status.
Dependencies
- Requires an API key credential for Octoparse API authentication.
Troubleshooting
- Common issues include invalid or expired API credentials, which will cause authentication failures.
- If the task or task group IDs are incorrect or missing, the API request will fail or return no data.
- Errors from the Octoparse API will be returned in the node output if 'Continue On Fail' is enabled, allowing troubleshooting of specific API error messages.