Cron jobs from disabled Magento_Analytics module is getting scheduled and returns an error

[AartiJogiya]

Description (*)

Magento_Analytics module has two cron jobs as mentioned below-

Configurations defined in crontab.xml are as below:

• Job name: analytics_subscribe Instance - "Magento\Analytics\Cron\SignUp" Method- "execute"

• Job name: analytics_collect_data Instance - "Magento\Analytics\Cron\CollectData" Method- "execute"

Cron expressions are stored in core_config_data table as mentioned below:

Job name	path	value
analytics_subscribe	crontab/default/jobs/analytics_collect_data/schedule/cron_expr	0
analytics_collect_data	crontab/default/jobs/analytics_collect_data/schedule/cron_expr	00 02 *

When Magento_Analytics module is disabled, It will not get instance and method from crontab.xml but having cron expression stored in core_config_data table so Magento_Cron module is scheduling cron jobs which returns “No callbacks found for cron job” error when job runs Here if a module is disabled then it should not schedule any jobs of that module.

Preconditions (*)

1. Magneto 2.4.2, 2.4-develop
2. In core_config_data table, make sure values are present for below paths:
   • crontab/default/jobs/analytics_subscribe/schedule/cron_expr
   • crontab/default/jobs/analytics_collect_data/schedule/cron_expr
3. Disabled Magento_Analytics module

Steps to reproduce (*)

1. Setup and run Magento cron

Expected result (*)

• analytics_subscribe and analytics_collect_data jobs should not be scheduled.

Actual result (*)

• cron jobs are scheduled in cron_schedules table and shows below errors:
  • No callbacks found for cron job analytics_subscribe
  • No callbacks found for cron job analytics_collect_data

Workaround

Magento_Cron module is generating cron schedules by preparing an array object having job-name, instance, method and scheduleby following below process:

• Reads crontab.xml file from all the enabled module and creates one array which will have job name, instance and method.

  • Related file paths:
    • magento/module-cron/Model/Config/Reader/Xml.php
    • magento/module-cron/Model/Config/Converter/Xml.php

• Reads the database and fetches cron expression stored in core_config_data table and it creates array having job name and schedule.

  • Related file paths:
    • magento/module-cron/Model/Config/Reader/Db.php
    • magento/module-cron/Model/Config/Converter/Db.php

These two arrays are getting merged using array_replace_recursive function which creates an array object and generates schedules to cron_schedules table.

Here, Magento_Analytics module is disabled so it will not get the first array having instance and method from crontab.xml. So it will only get second array having a job name and schedule from database and it generates cron schedule even if it doesn't have instance and method and therefore returns error "No callbacks found for cron job" from file: magento/module-cron/Observer/ProcessCronQueueObserver.php (function name- _runJob).

If module is disabled and not getting instance and method for cron job then it should not generate cron array object which will prevent scheduling job.

---

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

• [ ] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• [ ] Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• [ ] Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• [ ] Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• [ ] Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant[bot]]

Hi @AartiJogiya. Thank you for your report. To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

  :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

:clock10: You can find the schedule on the Magento Community Calendar page.

:telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

:movie_camera: You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

:pencil2: Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[m2-assistant[bot]]

Hi @engcom-Lima. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

• [ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• [ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• [ ] 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• [ ] 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• [ ] 5. Add label Issue: Confirmed once verification is complete.

• [ ] 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Lima]

Hi @AartiJogiya

We tried to reproduce the issue on 2.4-develop but were not able to do it.

Here is what we did:

1. We disabled Magento Analytics from Admin Panel: Stores > Configuration page under the General > Advanced Reporting tab.
2. We ran cron as suggested.
3. Checked cron_schedule table for any errors but couldn’t find any scheduled crons for cron jobs analytics_subscribe or analytics_collect_data.

So, in order to reproduce this on 2.4-develop, can you please check the above steps and let us know if you did things any differently or perhaps you can provide extra details for us to reproduce ?

[engcom-Lima]

Closing this issue as there has been no update from the reporter on the same.

[hostep]

@engcom-Lima: I think the issue does exist, I've seen it happening with other modules as well.

Therefore, could you please try the following instead of what you tried before:

• Install Magento with Analytics module enabled
• Configure the cron settings for this module and verify that the following 2 entries exist in the core_config_data table as was explained in the OP:
  • crontab/default/jobs/analytics_subscribe/schedule/cron_expr
  • crontab/default/jobs/analytics_collect_data/schedule/cron_expr
• Run the cron a few times
• Now disable the Analytics module (by manipulating the config.php file or running bin/magento module:disable ...)
• Run the cron a few times again
• Investigate the cron_schedule table, it should not get new entries for those two analytics cronjobs after the module was disabled.

[kanevbg]

This exists definitely in 2.3 it seem in 2.4 too

[hostep]

@engcom-Lima: could you please try this again with the steps mentioned above? Thanks! :)