# 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 module reports internal failures through a dedicated `croct` [logger channel](https://www.drupal.org/docs/develop/logging-and-errors). Failures during content fetching or query evaluation are recorded there.

View them under **Reports → Recent log messages** at `/admin/reports/dblog`, filtering by the `croct` type, or with [Drush](https://www.drush.org):

```sh
drush watchdog:show --type=croct
```

## Enable debug mode

Set the [`debug`](/reference/sdk/drupal/api/configuration#debug-prop) setting in `settings.php`:

**settings.php**

```php
$settings['croct.debug'] = TRUE;
```

Then rebuild the cache so Drupal applies the change:

```sh
drush cr
```

When enabled, the browser SDK logs detailed information to the console. See [Debugging](/reference/sdk/javascript/troubleshooting/debugging#enable-debug-mode) in the JavaScript SDK reference for the details.