> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xsoar-8-on-prem/8.9/investigate-and-respond-to-threats/incidents-and-indicators-investigation/investigate-an-incident/use-the-work-plan-in-an-investigation.md).

# Use the Work Plan in an investigation

The Work Plan is a visual representation of the running playbook assigned to the incident. Playbooks enable you to automate many security processes, such as managing your investigations and handling tickets. Work Plans enable you to monitor and manage a playbook workflow, and add new tasks to tailor the playbook to a specific investigation.

In an investigation, when you open the **Work Plan** tab you can see the playbook, the playbook name, and navigation tools.

By default, the **Follow** checkbox is checked, which allows you to see the playbook executing in real-time. The playbook moves when a task is completed.

In the Work Plan you can do the following:

| Action                      | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
| --------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Change the default playbook | <p>On the left-hand side of the window, select the playbook you want to run.</p><p>When changing the playbook, all completed tasks are removed and the new playbook will run. If you select playbooks several times you can view the history of which playbooks ran.</p>                                                                                                                                                                                                |
| Rerun the playbook          | When changing the playbook, select the current playbook to run again.                                                                                                                                                                                                                                                                                                                                                                                                   |
| View inputs and outputs     | View the inputs and outputs of each task that has run. You can't view inputs and outputs of any task that hasn't run.                                                                                                                                                                                                                                                                                                                                                   |
| Manage tasks                | <p>View, create, and edit a playbook task. For each task, you can do the following:</p><ul><li>Designate tasks as complete either manually or by running a script.</li><li>Assign an owner</li><li>Set a due date</li><li>Add comments and completed notes, as required.</li></ul><p>You can manage these tasks in the CLI by using the <code>/task</code> command. For more information about tasks, see <a href="/pages/in0azBzZwzGT95Ai0ysH">Incident Tasks</a>.</p> |
| Export to a PNG             | Export the Work plan to a PNG format for easy analysis.                                                                                                                                                                                                                                                                                                                                                                                                                 |

The color coding and symbols in the Work Plan help you to easily troubleshoot errors or respond to manual steps. The following table displays the playbook tasks and icons in the Work Plan.

{% hint style="info" %}

### Important

A playbook will not continue its execution path if a prior task has failed; you must resolve the failed task before subsequent tasks can run.
{% endhint %}

<details>

<summary>Playbook tasks and icons in the Work Plan</summary>

| Task                                                              | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
| ----------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| ![standard-task-old-logo.png](/files/WKOGPWczZX5y3uv7FEtX)        | <p><img src="/files/G5hPJbaDkJzZrZi2DLZn" alt="arrow.png"> <strong>Standard manual task</strong></p><p>An arrow with a light blue square background indicates a standard manual task. These tasks can ether be manual (no lightning bolt logo) or automated (with lightning bolt logo).</p><ul><li><p>Manual Standard task (no lightning bolt logo):</p><p>These tasks are used where usually it's not possible to automate them. You can add comments, assign them to an owner, and set a due date. The analyst who is responsible for the investigation needs to complete the task before the Work Plan can continue.</p></li><li><p>Automated Standard task (with lightning bolt logo):</p><p>A single command or script that is set to automatically run when the Work Plan reaches this step. Some scripts need arguments in order to run - make sure to set them up properly. If left empty, the analyst who is responsible for the investigation will need to complete them so the script will run and the Work Plancan continue.</p></li></ul> |
| ![condition-task-old-logo.png](/files/15BHlFIwg90rvztv2drR)       | <p><img src="/files/6SmpjfoDMU1KzYbbBXnn" alt="conditional_icon.png"> <strong>Conditional task</strong></p><p>A diamond icon in a purple square background indicates a conditional task, which is either an automated conditional task (with the lightning bolt logo) or a manual conditional task. These tasks are used as decision trees in your Work Plan.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
| ![data-collection-task-old-logo.png](/files/m3rGXERWFqK4jIbQi24h) | <p><img src="/files/CwMAWD6nwmfg8xHHaJwZ" alt="data_collection_icon.png"> <strong>Data collection task / Communication task</strong></p><p>The speech bubble in a turquoise background  indicates a data collection task. This task prompts the receivers to respond to a multi-question form and submit replies, even if they are not Cortex users.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
| ![sub-playbook\_task.png](/files/v29GBPWiJJkgkcXBICW8)            | <p><img src="/files/BleKcwl8TA1p56L11TM2" alt="sub-playbook_icon.png"> <strong>Sub-playbook task</strong></p><p>The workflow icon in a blue background indicates that the task is a playbook nested within the parent playbook. You can view that playbook by opening the task and selecting <strong>Open sub-playbook</strong>.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
| ![update-scripts-old-logo.png](/files/LNp8duGWXKqbgZPWOoES)       | <p><img src="/files/uCM8R4ajOliJkSDM60a5" alt="update_icon.png"> <strong>Task containing a deprecated script or needs to be updated</strong></p><p>Scripts that have updates or are deprecated are designated by a yellow triangle. You need to update the scripts and integration commands in playbook tasks to their most current version.</p><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>Tip</strong></p><p>You can configure your user preferences to automatically receive notifications about deprecated playbooks, sub-playbooks, and scripts. For more information, see <a href="/pages/Sthq4XQo3CHeyfJwI8gU">User details and preferences</a>.</p></div>                                                                                                                                                                                                                                                                                                                                    |
| ![skip-old-logo.png](/files/GGzxEczENDxjsi1bDT88)                 | <p><img src="/files/SjBeCjsBQGguhkuviWqF" alt="skip_icon.png"> <strong>Set to skip</strong></p><p>When a task is set to skip, the skip icon will be orange.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
| ![breakpoint-old-logo.png](/files/vikkerDxDJ83qZPKpQRu)           | <p><img src="/files/oKcAMnrQ1GsMnM1SsGpY" alt="breakpoint_icon.png"> <strong>Breakpoint</strong></p><p>When the playbook reaches a breakpoint, the task has an orange line at the top to indicate the breakpoint.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
| ![overriden-old-logo.png](/files/JjX238eWTt670HrJA99t)            | <p><img src="/files/qp4jJpLdBEBGsRZVUsgM" alt="overidden_icon.png"> <strong>Overridden inputs or outputs</strong></p><p>When a task is set to have overridden inputs or outputs, the word Input or Output appears in orange.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
| ![pending.png](/files/SxGY7voxtBfsW2MjZ3bq)                       | <p><img src="/files/NBxw27WaIEcLP7ku3cUA" alt="pending_icon.png"> <strong>Pending/in queue task</strong></p><p>When the Work Plan starts to run, all tasks that are about to be performed are gray.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
| ![running.png](/files/PdCJMPbqscnHtOMsFiSi)                       | <p><img src="/files/Oujqj7G3uzRFxwvBbanS" alt="running_icon.png"> <strong>Running/ in progress task</strong></p><p>A spinning circle inside the gray square indicates a running/in progress  task.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
| ![completed.png](/files/tVlw7rrVWDznrYGTaRPt)                     | <p><img src="/files/8K1qAH5980f9hl4YTd1h" alt="completed_icon.png"> <strong>Completed task</strong></p><p>The green square indicates a completed task.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
| ![waiting.png](/files/UHAQikcYH1TosdOinBxK)                       | <p><img src="/files/WFMx0v8rX0IrK5l6J9YV" alt="waiting_icon.png"> <strong>Waiting task</strong></p><p>The orange square indicates that the playbook is pending action.</p><p>If you hover on the icon on the top left corner, details about the specific reason this task is in waiting mode appears.</p><p>If the orange square is paired with the user icon ( <img src="/files/GCZ5rw681GQEsq5W60DW" alt="user_icon.png">), the task requires you to open it and manually mark it as complete.</p><p>If the orange square is paired with a speech bubble icon (<img src="/files/ABwewM8hgrigDyD9GFSU" alt="bubble_icon.png">), the task is waiting for a questionnaire to be completed.</p>                                                                                                                                                                                                                                                                                                                                                          |
| ![failed-old-logo.png](/files/Oi3exEvei14YN6RY5Jl7)               | <p><img src="/files/HV7vhFpNPLratY9Rtto9" alt="failed_icon.png"> <strong>Failed task</strong></p><p>The red warning icon indicates that the automation failed to complete as expected and requires manual inspection and troubleshooting. Contact your Cortex XSOAR administrator.</p><p>If you hover on the icon on the top left corner details about the specific problem appears.</p><p>If red warning icon is paired with the clock icon (<img src="/files/HnrVyGjuvCjUY9D1xU2s" alt="hourglass_icon.png">), the task’s SLA is overdue.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
| ![skipped-old-logo.png](/files/joH1qUgNqx1sdzPiNzAc)              | <p><img src="/files/V2kgwlEUunszeJfQPBrc" alt="skipped_icon.png"> <strong>Skipped task</strong></p><p>The task will look faded to indicate it was not executed. This can happen if this task was set to be skipped when an error occurs, or if it is in a branch that was not executed if a condition wasn’t met.</p>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |

</details>

**Add ad-hoc tasks to a Work Plan as part of your investigation**

As part of your incident investigation, within the Work Plan you can create tasks for a specific iteration of a playbook. The task type can be an automation or another playbook. For example, within a manual task, you might need to enrich some data and run an investigation playbook.

When you create a task, add a name, automation, and description. The name and description should be meaningful so that the task corresponds to the data that you are collecting.

1. In the Work Plan, go to the task where you want to add and click the + sign at the bottom right-hand corner of the task.

   The ad-hoc task is added after the task on which you clicked.
2. Select the task type.
   * Standard: Runs a single automation.
   * Playbook: Runs a playbook to enhance the investigation.

     The playbook functions as any playbook would and requires you to define the inputs and outputs, as well as any other details.
3. Click **Save**.
4. To run the Work Plan again, click the **Run again** icon.

**Example**&#x20;

For a phishing investigation, after the initial playbook run parses the email and extracts email addresses, as part of the manual investigation, you could use the **Email Address Enrichment - Generic v2.1** playbook as an ad-hoc playbook task to get more information about these email addresses.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-xsoar-8-on-prem/8.9/investigate-and-respond-to-threats/incidents-and-indicators-investigation/investigate-an-incident/use-the-work-plan-in-an-investigation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.