Log without details, only ERROR:

[PavelZ]

Hi, In the log file data/logs/espo-2026-03-23.log I can see the following errors:

[2026-03-23 04:44:06] ERROR:
[2026-03-23 04:44:06] ERROR:
[2026-03-23 04:51:20] ERROR:
[2026-03-23 04:51:20] ERROR:
[2026-03-23 05:12:43] ERROR:

However, I’m not sure how to properly analyze the issue. I also tried enabling printTrace, but it didn’t provide any additional useful information.

Does anyone have suggestions on how to debug this or what to check next?

[yuri]

Hi,

Maybe some customization or a 3rd party extension.

[max1987martin]

Hi, In the log file data/logs/espo-2026-03-23.log I can see the following errors:

[2026-03-23 04:44:06] ERROR:
[2026-03-23 04:44:06] ERROR:
[2026-03-23 04:51:20] ERROR:
[2026-03-23 04:51:20] ERROR:
[2026-03-23 05:12:43] ERROR:

However, I’m not sure how to properly analyze the issue. I also tried enabling printTrace, but it didn’t provide any additional useful information.

Does anyone have suggestions on how to debug this or what to check next? mcdvoice

Hello, PavelZ

It usually means the logger is being triggered, but the actual exception message isn’t being passed or is getting suppressed somewhere in the stack.

This usually means the error is triggered but the actual message isn’t being logged.

Try these quick checks:

Set log level to debug:
'logger' => ['level' => 'DEBUG'],
Check PHP/Apache/Nginx error logs — the real error is often there
Run cron manually:
php cron.php
If you have custom modules/hooks, check for empty exceptions like:
throw new \Exception();

Most of the time, this is caused by PHP fatal errors or custom code issues, not Espo itself.

Best Regard,
Max Martin