Decide whether one date changes or the habit changes
If a weekly review still belongs on Mondays but you cannot do it on one particular Monday, the decision is a date-specific exception. If you need it on another weekday from now on, the decision concerns the future rule. Distinguishing those scopes before saving helps avoid turning a one-off change into a different routine.
Ora documents weekly and monthly routines, exceptions and future series changes as Pro features. The earlier guide considers whether a routine fits into a busy day; this guide resolves which dates you intend to change.
Three Mondays, one exception
Imagine a twenty-minute personal review planned for Mondays November 2, 9 and 16, 2026. This is a fictional example: you will skip the 9th but retain the other two. No public holiday or external calendar is assumed.
Write the intended result before editing: “2nd, retain; 9th, skip; 16th, retain.” For that intention, look for editing one occurrence and check its original date. Do not change the every-Monday rule to resolve only the 9th.
Ora’s routine interface distinguishes editing one occurrence from editing the future series. Check that the proposal refers to the chosen day before saving. Skipping the occurrence does not mean completing the review: the work planned for that date has not been done.
An already added moment needs its own check
Moments created from routines are independent snapshots. Check whether the 9th is still an occurrence waiting to be added or already has a moment in a sphere. Editing the future rule retains already created moments; do not treat that edit as evidence the existing copy changed.
When editing an occurrence, check the selected sphere and then its resulting content. Copies in other spheres retain their data. If Ora flags recorded time, a focus session, dependencies or a calendar link, address that condition rather than deleting history to force an exception.
Clearing an exception restores the rule for future generation. That alone also does not move or change an already created moment. The final check returns to the particular dates and copies you intended to affect.
When the future rule really does need changing
Change the scenario: starting November 9, you want the review on Tuesdays. Your decision note now reads, “keep the earlier history; change the recurrence from the 9th.” Review the new rule’s effective date and upcoming occurrences before confirming.
Ora explains that a new future rule replaces later planned rule changes from that date. If you had already prepared another change for December, review it before saving. Exceptions and created moments remain, so check them separately if you intend to change those too.
An application preview still needs room in the day and must not create duplicates. Changing a series scope does not turn twenty planned minutes into recorded work.
Next, check the scope you chose
Before closing, return to your decision note: one date, a future rule or an existing copy. Check the affected day and another date you intended to keep. This procedure is a suggested review, not an observed interactive session or a guarantee about your plan.
Consult Ora’s current features before choosing Pro. Its public demo lets you explore the product; this guide does not claim that every paid feature is included or require connecting Google, Todoist or Outlook.