> For the complete documentation index, see [llms.txt](https://docs.atfinity.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.atfinity.io/guides/troubleshooting/why-is-my-proof-never-asked-for.md).

# Why is my Proof never asked for?

When moving through the Case Manager, you expect a proof to be asked for but it never is.

Here are some possibilities on how to solve the problem.

### Put Live

Changes you have made during your configuration only take effect once you have put them live. Therefore, make sure you have put your changes live. For more information, see [Putting Changes Live](broken://pages/-MKsl1gcJ3SJ7qdlcCcd).

### Add the proof to the process

Maybe your proof is not part of any process. Check if it has been added to the process you want to use.

Go to the process overview screen and open the process you would like the proof to be part of.

![](/files/SnbW0wAV1ogcagn29CTZ)

Select your proof in the ‘Proofs’ tab and put your changes live.

### Recheck the proof’s condition

Make certain that the proof’s condition is written correctly in terms of logic. It is sometimes helpful to write a condition stepwise when dealing with a very large and complex condition. Start small by writing only the first part of your condition. Put live and check if the proof appears in the case manager. If it did, keep adding parts to the condition and verify again. Once it disappears from the case, you know that the last piece you have added to your condition might be the problem.


---

# 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.atfinity.io/guides/troubleshooting/why-is-my-proof-never-asked-for.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.