rrule-recurring-tasks

To compute the next occurrence from an RRULE pattern, you parse the RFC 5545 string alongside a start timestamp, and the calculation returns the next scheduled datetime while enforcing UTC time handling to prevent timezone drift.

Yes, you can use simplified recurrence patterns like DAILY, WEEKLY, MONTHLY, and YEARLY instead of full RFC 5545 RRULE strings. Both formats are fully supported for defining flexible task scheduling rules.

Yes, python-dateutil handles UTC time and DST transitions correctly. The calculation enforces UTC-only time handling specifically to avoid timezone drift and daylight saving time issues during recurrence scheduling.

The best way to stop recurring task scheduling at a specific end date is to provide an optional end date parameter when parsing the RRULE pattern, which gracefully stops recurrence and validates occurrences within that bound.

RRULE next-occurrence calculations often fail during leap years or DST changes due to timezone drift. Enforcing strict UTC-only time handling and using validated RFC 5545 parsing ensures edge-case coverage for these transitions.