# Troubleshooting

Learn how to diagnose issues with your integration.

When something does not work as expected, the application logs are usually the first place to look for the cause.

> **Need help?**
>
> If you have any questions, please [contact us](https://croct.com/contact/support) for assistance or join our [community](https://croct.link/community) to get help from our team and other users.

## Inspect the logs

The bundle reports internal failures through the application logger, which Symfony provides through [Monolog](https://symfony.com/doc/current/logging.html). Failures during content fetching or query evaluation are recorded there.

In the development environment, you can watch them in real time:

```sh
php bin/console server:log
```

You can also read them directly from `var/log/dev.log`.

## Enable debug mode

In the development environment, [`debug`](/reference/sdk/symfony/api/configuration#debug-prop) mode is on by default, so the browser SDK already logs detailed information to the console. To force it on in any environment, set it explicitly:

**config/packages/croct.yaml**

```yaml
croct:
    debug: true
```

See [Debugging](/reference/sdk/javascript/troubleshooting/debugging#enable-debug-mode) in the JavaScript SDK reference for the details.