A repeated hour does not automatically expand your plan
Sunday 25 October 2026 had 25 elapsed hours in Europe/Madrid: at 03:00 summer time the clock returned to 02:00. Ora’s sphere retains its 24-hour capacity. These are different limits: the civil day’s duration and the plan’s allowed size.
Do not generalize this to every place or Sunday. The example is dated for that zone. The cover is illustrative; its clocks do not show the case’s exact times.
Two different instants are both called 02:30
Madrid’s first 02:30 that Sunday has offset UTC+02:00 and corresponds to 00:30 UTC. The second has offset UTC+01:00 and corresponds to 01:30 UTC. One hour passes between them although the wall clock shows the same numbers.
If someone proposes a 02:30 appointment, confirm which occurrence they mean before planning. Record the date, zone and UTC offset where needed; do not assume everyone chose the first.
Check elapsed duration before adding bubbles
Authored example: an interval from 02:00 UTC+02:00 to 03:00 UTC+01:00 on that date corresponds to 00:00–02:00 UTC, or 120 minutes. Subtracting only the local clock numbers gives 60 and loses the repeated hour.
This external calculation is neither an imported appointment nor output from a calendar integration. It clarifies the intended start and end instants. It also does not mean you should fill all 25 hours with tasks.
What Ora preserves when replanning
Ora replanning uses UTC intervals in the selected zone and accounts for 23- or 25-hour civil days while retaining the sphere’s 24-hour limit. Check the date, zone and ambiguous clock times before comparing and accepting a proposal. Applying and undoing replanning requires Pro.
A longer physical window does not permit saving 1,500 minutes in a 1,440-minute sphere. If your plan already fills 24 hours, choose what to adjust or leave out; do not add an hour as though the clock change expanded the product.
We promise neither guaranteed alarms nor real-provider or device acceptance. Those integration states are separate from this time calculation.
Prepare a plan you can review
Before accepting, keep three details clear: the sphere’s date, the Europe/Madrid zone and the occurrence selected for any repeated time. Compare elapsed durations separately from total planned capacity. Correct a mismatch before applying.
Explore Ora’s visual planning concept in the public demo without registration. This article explains a calendar case using code evidence and terminal checks; it does not claim visual or interactive acceptance of the workflow.