Hi Sumit
1) CRON jobs issue
I have forwarded your message to Prakash who will check the github you send.
I noticed that some admin text (e.g. “action created”) has been translated, and that the translations appears to be randomly displayed. See attached screen shot made from the English language. Are you sure this is not causing an issue?
There is no reason to translate all this admin texts. How can we have this fixed?
Each action uses a unique string, but if the same action is registered again, it will be displayed twice in the list. So, if a plugin or theme is registering the action without first checking whether it already exists, it will appear multiple times.
If you believe the multiple actions are created because of multiple languages, I don’t think that is the case. The action name itself is not translated anywhere, so it should remain the same across all languages. I believe the plugin or theme author would be in a better position to explain why the same action is being registered multiple times.
Ref: hidden link
see the screenshot: 17838030-Screenshot_2026_02_20_2.png
About the “action created” string being translated<br>
This happens because Action Scheduler localizes this string and then stores it directly in the database. On subsequent loads, the value is fetched from the database and displayed as-is.
I can even reproduce this behavior without WPML:
1. I disabled WPML.
2. I created a new admin user with the profile language set to French.
3. I registered an action using Action Scheduler, and the “action created” string was saved in French.
4. Then I logged in as another admin with the profile language set to English, but the “action created” string was still shown in French.
5. Please see the attached screenshots 17838030-Screenshot_2026_02_20.png showing the same behavior with WPML disabled.
This is exactly what is happening on your site. Multiple users or front-end calls in different languages cause the “action created” string to be saved in the current language. Once stored in the database, it is reused and displayed, regardless of the user language.
At this point, I’m not sure what we can do from the WPML side to prevent this. If WooCommerce stops localizing this string before saving it, the text would always remain in English. This appears to be mainly an Action Scheduler logic issue.
If you would like, I can report this behavior to the Action Scheduler plugin maintainers.