(copying my Github post)

Impacted versions: 15

Steps to reproduce:

Not sure how to reproduce it. I simply created a couple of ir.cron actions which I can trigger manually, but that never repeat on their execution date.

Current behavior:

In my production Odoo server, all my ir.cron scheduled actions are simply ignored. The "Next Execution Date" passes and nothing happens, the date doesn't change, and nothing shows up in the logs.

A couple of additional details that might help debugging:

• whenever I restart the server and reinstall the app (e.g.: when I deploy a new feature), the ir.cron actions are triggered once if their "Next Execution Date" was in the past. Then the "Next Execution Date" is updated, but it never triggers again as explained above.
• everything works fine in my dev server. This is simply a parallel deployment of Odoo on another machine, it has the exact same configuration with the differences being:
  • the database is a locally running Postgres instance, rather than the more robust option used in production (AWS Aurora)
  • the production server runs as a systemd service, whereas the dev server is launched by simply running the odoo command.
• when I trigger the actions manually, they work BUT the "Next Execution Date" is NOT updated.

Expected behavior:

ir.cron actions are triggered on their "Next Execution Date", or if skipped, at least something appears on the logs to help debug.