> For the complete documentation index, see [llms.txt](https://docs.eximee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eximee.com/documentation/documentation-en/eksploatacja-aplikacji/obsluga-procesow/eximeebpms-cockpit/debugowanie-procesow.md).
# Process debugging
The tools provided by EximeeBPMS Cockpit enable process debugging, in particular access to process variables and their current values.
After opening the detailed process view, all of its launched instances are displayed. On the diagram, active instances are marked with a blue circle, while the places where an incident occurred are marked with a red symbol.
{% hint style="info" %}
Incidents are also visible in the tab **Process Instances** in the column **State,** where a red marker appears next to the instances.
{% endhint %}
After clicking on the process number (in the column **ID**), details of a specific instance are displayed.
## Incidents
Tab **Incidents** shows the errors generated by a given process instance. The most important column during debugging is the column **Message**, where the message describing the incident is displayed. Proper analysis of it is crucial to diagnose the problem.
After clicking on the message content, a dialog window with the full message content will be displayed.
On the right side in the column **Action** there is a rolled-up arrow icon. Clicking it enables restarting the activity that ended with an incident.
## Variable values
In the **Variables** contains all variables and their values passed to the process. Clicking the red pencil icon allows manual editing of the value. Combined with the activity restart action, it is a useful tool for testing and debugging the process.
## Logs
While working with processes, it may happen that despite the time elapsed specified in **router-api**, the latest version of the process will not appear in EximeeBPMS. In such a case, the version visible in Cockpit may differ from the one available in Eximee Designer.
Information about errors that occurred during synchronization can be found in the logs ***process-handler-executor***.
---
# 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.eximee.com/documentation/documentation-en/eksploatacja-aplikacji/obsluga-procesow/eximeebpms-cockpit/debugowanie-procesow.md?ask=&goal=
```
`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.