> For the complete documentation index, see [llms.txt](https://developer.emporix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.emporix.io/vsm-guides/troubleshooting.md).

# Troubleshooting

- [Firewall Allowlisting](https://developer.emporix.io/vsm-guides/troubleshooting/allowlisting.md): See the details of firewall configuration for Value Stream Modeller.
- [Value Streams Debugger](https://developer.emporix.io/vsm-guides/troubleshooting/value-streams-debugger.md): Monitor process instances, filter them by directory or status, inspect step status, and replay or reply to single steps with role-based debugger access.
- [Generating a HAR File with Logs](https://developer.emporix.io/vsm-guides/troubleshooting/logs-generation.md): Learn how you can generate logs.
- [FAQ](https://developer.emporix.io/vsm-guides/troubleshooting/faq.md): See our troubleshooting guides.
- [Receiving Alerts for Scenario Errors](https://developer.emporix.io/vsm-guides/troubleshooting/faq/receiving-alerts.md): Learn how to get notified about errors.
- [Make Scenario Not Valid in VSM](https://developer.emporix.io/vsm-guides/troubleshooting/faq/make-scenario-not-valid.md): See how to proceed with an invalid Make scenario.
- [Value Streams Blocked by Scenario Errors](https://developer.emporix.io/vsm-guides/troubleshooting/faq/errors-handling.md): See how to proceed when a value stream is blocked with Make scenario errors.
- [Invalid Value Streams](https://developer.emporix.io/vsm-guides/troubleshooting/faq/invalid-value-streams.md): See how to fix an invalid value stream.
- [Import Fails - Make Data Stores](https://developer.emporix.io/vsm-guides/troubleshooting/faq/import-fails-make-data-stores.md): Reduce the Make data store size or set a module Limit so value stream import can complete in the target tenant.


---

# 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://developer.emporix.io/vsm-guides/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.