Scheduling a release for 09:00 sounds simple. Then the clocks go forward, and the release starts arriving at 10:00. Or your server is in another country and "09:00" turns out to mean the middle of the night for your members. Or a monthly release set for the 31st quietly skips February.
These are small details, but members notice when releases drift. This guide explains how time zones, daylight saving, month-end dates and leap years affect scheduled releases, and what a reliable scheduler should do about each.
Plan in local time, store in UTC
The most reliable approach uses two clocks:
- The website's own time zone for planning and display. You set "09:00, Europe/London" because that is when your members are around.
- UTC for storing and running releases. UTC never changes for daylight saving, so the server always has one steady clock to work from.
Each time a release is planned, the scheduler works out what 09:00 local time means in UTC on that particular date. In winter, 09:00 in London is 09:00 UTC. In summer it is 08:00 UTC. The members see 09:00 all year round.
The mistake to avoid is storing "08:00 UTC" once and repeating it forever. That is right for half the year and an hour out for the other half.
Use named time zones, not fixed offsets
Choose a named zone such as Europe/London or America/New_York, not a fixed offset like "UTC+1". A named zone knows when daylight saving starts and ends in that region; a fixed offset does not. Different countries change their clocks on different dates, so this matters if your sites serve different regions.
Sites in different time zones
If you run several sites, each should have its own time zone. A site aimed at UK members and one aimed at US members can both release at 09:00 local time, which are several hours apart in reality.
| Site time zone | Local release | UTC in January | UTC in July |
|---|---|---|---|
| Europe/London | 09:00 | 09:00 | 08:00 |
| America/New_York | 09:00 | 14:00 | 13:00 |
| Australia/Sydney | 09:00 | 22:00 (previous day) | 23:00 (previous day) |
Notice that Sydney moves in the opposite direction, because its summer is in January. This is exactly the kind of thing a scheduler should handle for you. For advice on choosing the time itself, see how often a member site should add new content.
The two awkward daylight saving hours
The skipped hour in spring
When clocks go forward, one local hour does not exist. In the UK, 01:00 jumps straight to 02:00. A release set for 01:30 that night has no real time to run at. A good scheduler moves it to the next valid time rather than missing it.
The repeated hour in autumn
When clocks go back, one local hour happens twice. A release at 01:30 could appear to be due twice. A good scheduler runs it once, and uses locking so the same release can never be run a second time.
The simplest way to avoid both cases is to schedule releases outside the early hours where clocks change. That is good practice for members anyway.
Month-end dates and leap years
Monthly and yearly schedules have their own traps:
- The 31st. A release on the 31st of every month should run on the last day of shorter months (30 April, 28 or 29 February), not be skipped or pushed into the next month.
- The 29th to 31st in February. The same rule applies to any date February does not have.
- 29 February. A yearly release on 29 February needs a sensible rule for non-leap years, usually 28 February.
- Drift. After a short month, the schedule should return to the 31st the following month, not stay stuck on the 30th.
Intervals in days versus months
"Every 30 days" and "every month" are not the same. A 30-day interval slowly moves through the calendar, landing on a different date each month. A monthly interval stays on the same date. Choose whichever matches what you have told members. The same goes for weeks: "every 7 days at 09:00" should still mean 09:00 local time after the clocks change, even though one of those weeks is an hour shorter or longer.
Check before the clocks change
Twice a year it is worth a quick look at the next few upcoming releases for each site, especially sites in different regions. Confirm the local times still show as expected. It takes a minute and catches any schedule that was set up with a fixed offset by mistake.
Releases need a reliable clock
All of this only works if releases are run by a scheduled task on the server, checking regularly whether anything is due. Releases triggered by page visits arrive late on quiet nights, and can't be trusted around clock changes. It also helps to have a clear rule for releases missed during server downtime: run the latest missed release, catch up within a limit, or skip. Our guide on why scheduled releases need a cron job explains the setup.
How Members CMS handles this
In Members CMS every drip schedule has its own release time and time zone, set per website. Release times are stored in UTC and planned in the site's time zone, with daylight saving, leap years and month-end dates handled by the scheduler. Releases are run by the server's cron job, locked so they never run twice, and a missed-release policy decides what happens after downtime.
Upcoming Releases shows planned times so you can check them before they happen, and Release History records both the planned and actual time of every release. As each release runs, the new content appears in that site's members area and on its tour through the connector.
Frequently asked questions
Why store release times in UTC?
UTC never changes for daylight saving, so it gives the server one reliable clock. The website's own time zone is then used to show and plan local release times.
What happens to a monthly release set for the 31st?
In months without a 31st it should run on the last day of the month rather than being skipped or pushed into the next month.
What about releases during the hour that is skipped when clocks go forward?
A good scheduler moves them to the next valid time instead of missing them, and makes sure the repeated hour in autumn does not run a release twice.
