Skip to main content

Get data offset

Sophie avatar
Written by Sophie
Updated over a week ago

Definition and Usage

Get data offset retrieves the current data offset of a cloud task in Octoparse. This command allows you to check how much data has been processed in a specific Octoparse task, which is useful for monitoring task progress and data extraction status.


Parameter Values

Input parameters

Parameter

Description

Required

Options / Notes

Octoparse account

Select an access token obtained by "Log in to Octoparse"

Yes

Must be authenticated via "Log in to Octoparse" command first

Task ID

Enter Octoparse task ID(s) to check (separate multiple IDs with ";")

Yes

You can check multiple tasks by separating IDs with semicolons

Error handling

Parameter Name

Description

Throw error & stop

When an error occurs, the action will trigger an error and stop the execution of the entire app.

Retry command

If an error occurs, the action will retry the command in an attempt to resolve the issue and continue the process.

Ignore error & continue

When an error occurs, the action will be ignored, and the workflow will continue without interruption.

Variables produced

This action produces a variable that stores the data offset value of the specified Octoparse task(s).


Using Variables in Conditions

You can use the {x} notation to insert variables into parameter fields. For the Task ID field, you can use previously defined variables that contain task identifiers. The output variable can be used in subsequent actions to track progress or make decisions based on the current data offset.


Notes

  • Before using this command, ensure you have successfully logged into Octoparse using the "Log in to Octoparse" command.

  • The task ID must be valid and accessible with the provided Octoparse account credentials.

  • If multiple task IDs are provided, the command will return offset information for all specified tasks.

  • This command is particularly useful for monitoring large data extraction jobs and implementing checkpoint logic in your automation workflows.

Did this answer your question?