> For the complete documentation index, see [llms.txt](https://docs.wedolow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wedolow.com/documentation/ressources/troubleshooting.md).

# Troubleshooting

<details>

<summary>Why beLow CTL does not start anymore (no tray)?</summary>

There might have been a problem while releasing the lock preventing it from opening multiple times.

To release the lock, remove the tray.lock file for your platform:

${HOME}/.config/wedolow/tray.lock%USERPROFILE%\AppData\Roaming\wedolow\tray.lock

If the problem persists, please contact us at <support@wedolow.com>.

</details>

<details>

<summary>Why the user interface does not run because of missing libraries on Windows?</summary>

You may have missed installing the Visual Studio C++ Redistributable 2017 listed in the [requirements](https://docs.wedolow.com/below-technical-documentation/readme/installation-instructions/windows/requirements).

</details>

<details>

<summary>Why a CMake build may fail on Windows?</summary>

This can happen because of a possibly faulty compilation database generated by CMake on Windows when injecting preprocessor variable definitions with certain syntax, for example:

```cmake
add_definitions(-DLIB_HEADER_FILE="lib.h")
```

You may find ways to overcome this issue in the compatibility guide: <https://docs.wedolow.com/below-technical-documentation/compatibility-guide/cmake#windows-specificities>

</details>

<details>

<summary>Why jobs fail and log archives are empty?</summary>

This occurs when the time on the machine where the runners run and the machine where the server runs differ (known date/time mismatch).

* For Windows full-desktop usage: check that Windows and WSL time are synced.
* For distributed usage: check time sync for all machines. If they are not in sync, enable internet time synchronization when possible or set the time manually so all machines match the same time zone.

</details>


---

# 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.wedolow.com/documentation/ressources/troubleshooting.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.