> ## Documentation Index
> Fetch the complete documentation index at: https://www.octoparse.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Start Or Stop Task

> Start or stop an existing Octoparse task through AgentTools.

<Info>
  The request body, generated cURL example, and response schema are shown in the API panel.
</Info>

Start or stop an existing Octoparse task through AgentTools.

<Steps>
  <Step title="Locate the task">
    Use `searchTasks` when the task ID is not already known.
  </Step>

  <Step title="Request an action">
    Send `action` as `start` or `stop`.
  </Step>

  <Step title="Continue with export">
    Use `exportData` when response guidance indicates data may be available.
  </Step>
</Steps>

```text theme={null}
searchTasks -> startOrStopTask -> exportData
```

<CardGroup cols={2}>
  <Card title="Request body" icon="braces">
    `taskId` and `action` are required.
  </Card>

  <Card title="Actions" icon="play">
    Allowed `action` values are `start` and `stop`.
  </Card>
</CardGroup>

<AccordionGroup>
  <Accordion title="Status values">
    `start_requested` and `stop_requested` mean the request was accepted.

    `already_running` and `already_stopped` mean no state change was needed.

    `start_rejected`, `stop_rejected`, and `invalid` require client-side handling or user review.
  </Accordion>

  <Accordion title="Response guidance">
    Follow `retryGuidance`, `suggestedNextCall`, `workflow`, and `toolHint` instead of hard-coding polling intervals.
  </Accordion>
</AccordionGroup>