> For the complete documentation index, see [llms.txt](https://help.pickzen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.pickzen.com/guides/nocode/builder/simulation.md).

# Simulation

In this panel we can simulate combinations of answers to ensure the logic works as expected.

For example, once our logic is defined, we can see that selecting different inputs, we get different results:

![](/files/-MA_vNlgao99XEW1bN8G)

![](/files/-MA_vaHKC85NoD49XW9D)

The selectable inputs are the aliases we defined in the Aliases tab. They can also be form fields:

![](/files/-MA_w3Hz58L3TJzxUz7Y)

### Console

In the browser console, we can see more information that can help us to troubleshoot issues. If we display it, we can see traces with the "Nocode simulation scope" prefix:

![](/files/-MA_wcqgRIXlZcCzOjy9)

In this *scope*, are stored all variables used to execute the logic.


---

# 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://help.pickzen.com/guides/nocode/builder/simulation.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.