This article provides patches for the Advanced Reporting cron jobs issues in Adobe Commerce, which can cause a 404 error for customers trying to access Advanced Reporting.
Adobe Commerce (all deployment options) 2.3.x
A customer gets a 404 error when they attempt to access Advanced Reporting and there are errors in the logs associated to analytics_collect_data job
.
The patches are compatible (but might not solve the issue) with the following Adobe Commerce versions and editions:
To fix the issue, please apply the relevant patch attached to this article. To download it, click the following links:
To check which patch to use:
grep analytics_collect_data var/log/support_report.log var/log/support_report.log.1.gz
Error |
Patch |
report.CRITICAL: Error when running a cron job {"exception":"[object] (RuntimeException(code: 0): Error when running a cron job at /srv/public_html/vendor/magento/module-cron/Observer/ProcessCronQueueObserver.php:327, TypeError(code: 0): substr_count() expects parameter 1 to be string, null given at /srv/public_html/vendor/magento/module-page-builder-analytics/Model/ContentTypeUsageReportProvider.php:106)"} []OR report.ERROR: Cron Job analytics_collect_data has an error: substr_count() expects parameter 1 to be string, null given. Statistics: {"sum":0,"count":1,"realmem":0,"emalloc":0,"realmem_start":224919552,"emalloc_start":216398384} [] []
|
ApplyMDVA-19391_EE_2.3.1_COMPOSER_v1.patch.zip, clear cache and wait 24 hours for the job to run again and try again. |
Failed to open file /tmp/analytics/tmp/../tmp/../tmp/../tmp/../tmp/../tmp/../tmp/../tmp/../tmp/../tmp/../tmp/../tmp/../tmp/../tmp/../tmp/../tmp/../tmp/../ |
ApplyMDVA-15136_EE_2.2.6_COMPOSER_v1.patch.zip, clear cache and wait 24 hours for the job to run again and try again. |
Not valid cipher | ApplyMDVA-18980_EE_2.2.6_COMPOSER_v1.patch.zip, clear cache and wait 24 hours for the job to run again and try again. |
Unzip the file and follow instructions in How to apply a composer patch provided by Adobe.