The 31st is not every month’s last day
In Ora monthly routines, a day absent from a month is skipped without rolling into the next month. Choosing the 31st does not by itself create a February 28 or March 1 occurrence. Check the specific date before treating the month as prepared.
Routines belong to Pro. The public presentation documents weekly and monthly rules, exceptions and a preview before application. The absent-day guidance is included in the published routine-configuration text. This guide describes that rule; it does not claim account or browser interaction testing.
Three months without inventing a date
Fictional example: you prepare a monthly materials review, choosing the 31st every month from January 2027. January has a 31st, February does not and March has one again. Skipping February neither completes the review nor means Ora automatically moved it.
Also distinguish the rule from an activity applied to a particular day. A date matching recurrence does not establish that you accepted its preview, reserved time or finished the work. Review those decisions separately.
- January 31: the date exists and can match this example’s rule.
- February: the chosen day is absent; do not assume automatic month-end application.
- March 31: the chosen day exists again; its specific application still needs review.
Decide what monthly means for the commitment
If you need a review sometime in each month, you can deliberately choose a day present in every month, such as the 28th, and check when the change should take effect. That changes your rule rather than expressing “last day” in another way.
If the commitment requires the actual last day of every month, check the calendar and prepare the appropriate dates. We claim neither a last-day selector nor automatic business-day adjustment in Ora. Do not change an external deadline merely to fit recurrence.
Check date and capacity before applying
Open preparation for the date you intend to use and read the proposal before accepting it. Check that the work appears only once and its reservation fits alongside the rest of the day. Ora retains a 24-hour capacity per sphere; repetition creates no additional time.
A skipped routine and a completed task are different states. If you did the work another way, record what actually happened in your plan; an absent bubble does not establish completion.
A calendar rule and a choice you control
This differs from changing one Monday exception: you are choosing which dates the monthly rule generates. Retain earlier history when preparing a future change and review its scope before accepting.
Check current features to separate available functions from integrations awaiting validation. Before reserving work for the next short month, ask whether you need the number 31 or a review that takes place every month.