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.

Croct's mascot winking
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 package reports internal failures through the application logger, which Laravel provides through Monolog. 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:

php artisan pail

Enable debug mode

The debug 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
CROCT_DEBUG=true

See Debugging in the JavaScript SDK reference for the details.