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

# Using AI to troubleshoot failed jobs

{% hint style="info" %}
**Required workspace permission:** Download job logs
{% endhint %}

For the the following types of jobs:

* Sensitivity scans
* Data generation jobs
* Upsert jobs
* Collection scans

You can ask for AI help to troubleshoot the failure.

On the job details, to start the AI troubleshooting, click **Ask AI**.

Structural sends the job log information to the LLM, which returns an analysis of the failure and suggested next steps.

The diagnosis includes an **Open in Agent chat** option to allow you to use the Structural Agent to continue the conversation.


---

# 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.tonic.ai/app/workspace/jobs/jobs-ai-troubleshooting.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.