> For the complete documentation index, see [llms.txt](https://docs.veedna.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.veedna.com/unifai/missions/troubleshooting-missions.md).

# Troubleshooting Missions

Missions are auto-executable workflows. If you run into a troubleshooting situation, use the scenarios below to identify the issue and follow the recommended steps. If you need further assistance, reach out to Lineaje Support at: <support@lineaje.com>.

<details>

<summary>Abort a mission</summary>

If you want to pause your current mission and switch to a different activity, click the Abort Mission button located in the bottom left corner of the screen. Aborting a mission pauses your progress. You can return later and continue from where you left off.

</details>

<details>

<summary>Agent is taking too long</summary>

A typical run time for an agent is \_\_\_. If it takes longer than that, do \_\_\_\_\_

</details>

<details>

<summary>The mission freezes and stops making progress</summary>

If the mission stops responding or the progress bar no longer moves, the system may be stuck on a background task.

What you can do:

* Abort the mission and run it again.
* ?

</details>

<details>

<summary>Re-run the mission and re-enable policies</summary>

?

</details>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.veedna.com/unifai/missions/troubleshooting-missions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
