> For the complete documentation index, see [llms.txt](https://docs.hesh.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hesh.app/manuals/production/production-workflow/task/related-tasks-section.md).

# "Related tasks" section

## Overview

The "**Related tasks"** section provides a clear view of the tasks connected to your current task. It displays previous tasks that have been completed or are still in progress, as well as upcoming tasks in your workflow. This visibility helps you navigate and track the progress of tasks seamlessly.

<figure><img src="/files/H5cx6EitNr2jnsGky7hZ" alt=""><figcaption></figcaption></figure>

### Key features

* **View previous and next tasks**: Easily navigate through the tasks in the workflow in sequential order. This allows you to monitor the progression of tasks and understand their interdependencies.
* **Fail tasks**: Easily fail any tasks in the flow directly from the "Related tasks" section. Simply click on the "Manage failed tasks" button to view all tasks. This allows you to address issues promptly without navigating away from your current task.
* **Navigate to specific task/component in the flow:** There’s no need to return to the main canvas to access related tasks or components. Simply click on the task or component you wish to open. This will take you directly to the selected item, saving you time.

## **Use cases**

### **Opening task/component**

1. Click on the task/component you want to open

{% @arcade/embed flowId="KPyYClO71RezFyzvYhxx" url="<https://app.arcade.software/share/KPyYClO71RezFyzvYhxx>" %}

### Clicking "Manage failed task"

1. Click "Manage failed tasks" button

{% @arcade/embed flowId="Gx8ZRI8AYh5qYlEmfNXy" url="<https://app.arcade.software/share/Gx8ZRI8AYh5qYlEmfNXy>" %}


---

# 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://docs.hesh.app/manuals/production/production-workflow/task/related-tasks-section.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.