Skip to content

If cronjob added to the multiple groups you can't disable one of them. It edits wrong one. #39785

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
5 tasks
Genaker opened this issue Apr 2, 2025 · 2 comments
Labels
Reported on 2.4.x Indicates original Magento version for the Issue report. Triage: Dev.Experience Issue related to Developer Experience and needs help with Triage to Confirm or Reject it

Comments

@Genaker
Copy link

Genaker commented Apr 2, 2025

Preconditions and environment

  • Magento version ANY
  • Anything else that would help a developer reproduce the bug

If cronjob added to the multiple groups you can't disable one of them. it disables wrong one.
When you are editing one job it will change another one with the same Job Code from another group

Reproduce:
Create cron job with the same job code added to different croun groups:

There is extension with an example of such feature:

https://github.com/TechNWeb/TNW_Salesforce/blob/master/etc/crontab.xml

Image

Steps to reproduce

two jobes with the same job code in different groups:
If cronjob added to the multiple groups you can't disable one of them. it disables wrong one.

Expected result

edits/disables correct group

Actual result

wrong one

Additional information

No response

Release note

No response

Triage and priority

  • 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”.
Copy link

m2-assistant bot commented Apr 2, 2025

Hi @Genaker. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.


Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

@Genaker
Copy link
Author

Genaker commented Apr 2, 2025

Even from the edit URL we can see it is selected by job code not by ID:

admin/cronjobmanager/config/edit/job_code/staging_synchronize_entities_period/key/sadasdasd/

but we have two jobs with the same code now. Please fix ASAP

@engcom-Bravo engcom-Bravo added the Reported on 2.4.x Indicates original Magento version for the Issue report. label Apr 3, 2025
@github-project-automation github-project-automation bot moved this to Ready for Confirmation in Issue Confirmation and Triage Board Apr 3, 2025
@engcom-Bravo engcom-Bravo added the Triage: Dev.Experience Issue related to Developer Experience and needs help with Triage to Confirm or Reject it label May 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Reported on 2.4.x Indicates original Magento version for the Issue report. Triage: Dev.Experience Issue related to Developer Experience and needs help with Triage to Confirm or Reject it
Projects
Status: Ready for Confirmation
Development

No branches or pull requests

2 participants