Content release triggered at incorrect date/time #24727
Description
Node Version
22.20.0
NPM/Yarn/PNPM Version
NPM 10.9.3
Strapi Version
5.23.3 (Enterprise)
Operating System
Docker/Podman/LXC
Database
MySQL
Javascript or Typescript
Typescript
Reproduction URL
No response
Bug Description
Today we experienced an unexpected content release, occurring before its scheduled execution date. The following is an excerpt from the database strapi.strapi_releases table (MySQL).
| id | released_at | created_at | updated_at | published_at | scheduled_at | timezone | status |
|---|---|---|---|---|---|---|---|
| 82 | 2025-10-29 03:00:02.349000 | 2025-10-27 16:54:42.910000 | 2025-10-29 03:00:02.349000 | 2025-10-27 16:54:42.910000 | 2025-10-29 11:00:00.000000 | Europe/Amsterdam | done |
As you can see, the released_at value does not match the scheduled_at value. No manual release was triggered at this time. There were no other releases scheduled on this day as well. In our console logs we can find the following:
[2025-10-29 03:00:00.030] [32minfo[39m: [Content Releases] Starting to publish release [redacted, but matching 82]
Steps to Reproduce
We weren't able to reproduce it, but I'm assuming it is something like the following:
- Schedule a release in the future
- Wait for the CRON job to mistakenly execute the release, possibly on the correct day, but the wrong time.
Expected Behavior
I expect a scheduled release to be executed at the correct day and time, and that there should be no significant difference between the scheduled_at value and the actual released_at value.
Logs
2025-10-29T02:00:05.6455368Z [2025-10-29 03:00:00.030] [32minfo[39m: [Content Releases] Starting to publish release [redacted, but matching 82]Code Snippets
No response
Media
No response
Additional information
No response
Confirmation Checklist
- I have checked the existing issues for duplicates.
- I agree to follow this project's Code of Conduct.