---
title: "Individual cron jobs are not detailed in the logs"
date: "2025-02-05T23:47:50+00:00"
summary:
image:
type: "article"
url: "/acquia-cloud-platform/help/93326-individual-cron-jobs-are-not-detailed-logs"
id: "f71454b6-79ca-46c0-b2a5-a85b75620fa9"
---

**Issue**
---------

When checking the cron log files and/or the drupal-watchdog ones, there is no detail on the individual cron jobs that ran, only the following entries:

    Mar 31 06:26:05 server-XXX subenv: http://XXX|1617171965|cron|127.0.0.1|http://XXX||0||Cron run completed.
    Mar 31 06:27:03 server-XXX subenv: http://XXX|1617172023|cron|127.0.0.1|http://XXX||0||Cron run completed.
    Mar 31 06:29:04 server-XXX subenv: http://XXX|1617172144|cron|127.0.0.1|http://XXX||0||Cron run completed.
    ...

Whereas you would like to get more detailed log entries, as:

    Mar 30 13:54:04 server-XXX subenv: http://XXX|1617112444|cron|127.0.0.1|http://XXX||0||Starting execution of acquia_connector_cron().
    Mar 30 13:54:04 server-XXX subenv: http://XXX|1617112444|cron|127.0.0.1|http://XXX||0||Starting execution of comment_cron(), execution of acquia_connector_cron() took 0.6ms.
    Mar 30 13:54:04 server-XXX subenv: http://XXX|1617112444|cron|127.0.0.1|http://XXX||0||Starting execution of dblog_cron(), execution of comment_cron() took 6.63ms.
    Mar 30 13:54:04 server-XXX subenv: http://XXX|1617112444|cron|127.0.0.1|http://XXX||0||Starting execution of field_cron(), execution of dblog_cron() took 1.48ms.
    Mar 30 13:54:04 server-XXX subenv: http://XXX|1617112444|cron|127.0.0.1|http://XXX||0||Starting execution of file_cron(), execution of field_cron() took 1.67ms.
    Mar 30 13:54:04 server-XXX subenv: http://XXX|1617112444|cron|127.0.0.1|http://XXX||0||Starting execution of history_cron(), execution of file_cron() took 39.63ms.
    Mar 30 13:54:04 server-XXX subenv: http://XXX|1617112444|cron|127.0.0.1|http://XXX||0||Starting execution of layout_builder_cron(), execution of history_cron() took 1.69ms.
    Mar 30 13:54:04 server-XXX subenv: http://XXX|1617112444|cron|127.0.0.1|http://XXX||0||Starting execution of locale_cron(), execution of layout_builder_cron() took 11.59ms.
    Mar 30 13:54:04 server-XXX subenv: http://XXX|1617112444|cron|127.0.0.1|http://XXX||0||Starting execution of node_cron(), execution of locale_cron() took 0.61ms.
    Mar 30 13:54:04 server-XXX subenv: http://XXX|1617112444|cron|127.0.0.1|http://XXX||0||Starting execution of search_cron(), execution of node_cron() took 10.56ms.
    Mar 30 13:54:04 server-XXX subenv: http://XXX|1617112444|cron|127.0.0.1|http://XXX||0||Starting execution of search_api_cron(), execution of search_cron() took 27.35ms.
    Mar 30 13:54:04 server-XXX subenv: http://XXX|1617112444|cron|127.0.0.1|http://XXX||0||Starting execution of update_cron(), execution of system_cron() took 44.06ms.
    Mar 30 13:54:04 server-XXX subenv: http://XXX|1617112444|cron|127.0.0.1|http://XXX||0||Execution of update_cron() took 42.97ms.
    Mar 30 13:54:04 server-XXX subenv: http://XXX|1617112444|cron|127.0.0.1|http://XXX||0||Cron run completed.

**Cause and Resolution**
------------------------

This might be due to the fact that you have not checked the option `Detailed cron logging` from the cron configuration page on your Drupal website `/admin/config/system/cron`.  
  

![Checkbox for "Detailed cron logging" under "Cron Settings," with description about logging run times to watchdog.](https://acquia.widen.net/content/d9040a25-2989-4269-865b-7a6e0dfd4957/web/ka0Pb0000008gjd00N6g00000VCdgi0EM6g000002WpDq.png)

Checking this option will likely solve this.