Next Start Date/Remaining Time for Recurring Events Calculates Incorrectly
Posted: Thu Mar 28, 2024 6:30 pm
The issue: The next Start Date and Remaining Time for random repeating Events calculate too far into the future. These Events also will not disappear when "Complete" is selected in the "Task Reminder" dialogue box.
Example: An Event which should calculate to recur on the following day will calculate to a random date in the future, anywhere from two days ahead to months ahead. [This behavior is not exclusive to Events that should recur on the following day, it can be any Event, regardless of the next occurrence.]
The problem: These random Events need to be manually corrected. Sometimes this fixes the issue, sometimes it does not, and the same error will repeat. Recreating the Event, either on the same tasklist or a different one, sometimes corrects the problem, and sometimes not.
This issue occurs only with a small percentage of Events, not every one. Which Events will be affected is impossible to predict. None of the affected Events are constructed in a manner unique to themselves, they are composed similarly to Events that never have this issue.
A workaround for this issue does not seem evident. Help with this would be welcome.
Example: An Event which should calculate to recur on the following day will calculate to a random date in the future, anywhere from two days ahead to months ahead. [This behavior is not exclusive to Events that should recur on the following day, it can be any Event, regardless of the next occurrence.]
The problem: These random Events need to be manually corrected. Sometimes this fixes the issue, sometimes it does not, and the same error will repeat. Recreating the Event, either on the same tasklist or a different one, sometimes corrects the problem, and sometimes not.
This issue occurs only with a small percentage of Events, not every one. Which Events will be affected is impossible to predict. None of the affected Events are constructed in a manner unique to themselves, they are composed similarly to Events that never have this issue.
A workaround for this issue does not seem evident. Help with this would be welcome.