> For the complete documentation index, see [llms.txt](https://help.clause9.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.clause9.com/qna/q-and-a-faq.md).
# Q\&A - FAQ
My Q&A warns about save failures
If the message you get is akin to the following
(or perhaps *“deleted card”*) then you are facing the problem that you still refer to some question/card somewhere, while that question/card has been deleted in the meantime.
The easiest way to solve it, is to completely expand all cards and all change sets, and check where orange selection boxes appear. You can do so by clicking on the expansion arrows while both Shift and Alt (Option on Mac) are held down. For example:
will show the following, indicating that the placeholder still happens to refer to some deleted question:
Tip: you can prevent such errors from happening by selecting a question (or card), and then checking the contents of the Dependencies pane in the Q\&A. In the example scenario above, the question that was deleted, actually showed the following before it got deleted:
---
# 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://help.clause9.com/qna/q-and-a-faq.md?ask=&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.