Troubleshooting

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 for assistance or join our community to get help from our team and other users.

Inspect the logs

The module reports internal failures through a dedicated croct logger channel. 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:

drush watchdog:show --type=croct

Enable debug mode

Set the debug setting in settings.php:

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

Then rebuild the cache so Drupal applies the change:

drush cr

When enabled, the browser SDK logs detailed information to the console. See Debugging in the JavaScript SDK reference for the details.