> For the complete documentation index, see [llms.txt](https://docs.prst.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prst.ai/elements-and-features/executions.md).

# Executions

## Overview

Prst.ai provides an advanced system of executions tracking based on tasks. using our executions history it is possible to track all activity in your system related to integrations with AI.

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

## Execution Task&#x20;

The PRST Task is an entity that combines information about [Prompt](/elements-and-features/prompts.md), [Connector](/elements-and-features/connectors.md), user or [API credentials](/elements-and-features/api-credentials.md) and keeps the result and logs of the execution.&#x20;

We also provide a several ways to execute task: **sync or async**. Depending on option the generation result will be available during one connection session or after processing.&#x20;

### Life-cycle

<figure><img src="/files/gfjSuEbCn1MvuFYm95PU" alt="" width="375"><figcaption></figcaption></figure>

## Debug Details

Prst.ai allows to see all execution details  through the Debug Details. In the details tab it's possible to get information about used prompt and used connector, as well and debug information.&#x20;

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


---

# 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:

```
GET https://docs.prst.ai/elements-and-features/executions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.