Recurring Date Generator

Worked example

A monthly rule pinned to day 31, starting January 31, 2027, generates January 31 first, then February 28, constrained to that month's own last real day since February never has a 31st, then March 31 once a full 31-day month comes around again. Switch the same rule to the roll-forward policy instead of constrain, and that February occurrence moves to March 3 instead of February 28, spilling the missing three days into the following month rather than landing on February's own last day. Both policies are equally valid interpretations of "day 31, every month." They simply resolve the same underlying gap differently, which is exactly why the choice is a visible input here rather than a silent default buried in the calculation.

Common mistakes

• Assuming "day 31, every month" always lands on the 31st. In a shorter month it either constrains to that month's last day or rolls forward, depending entirely on the policy chosen.
• Requesting more occurrences than the generator's own bound allows, which is reported directly rather than returning a silently truncated list with no explanation.

Limitations

The generated preview is bounded to 500 occurrences or 5 years, whichever comes first, to keep the output fast and reviewable. This generates dates only. It does not send reminders or notifications of any kind.