# 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 package reports internal failures through the application logger, which Laravel provides through [Monolog](https://laravel.com/docs/logging). Failures during content fetching or query evaluation are recorded there.

You can read them in `storage/logs/laravel.log`, or watch them in real time with [Laravel Pail](https://laravel.com/docs/pail):

```sh
php artisan pail
```

## Enable debug mode

The [`debug`](/reference/sdk/laravel/api/configuration#debug-prop) option follows your application's debug mode by default, so the browser SDK already logs detailed information to the console in local development. To force it on in any environment, set it explicitly in your `.env` file:

**.env**

```bash
CROCT_DEBUG=true
```

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