A scheduled path belongs to a record event, while a schedule-triggered flow starts a recurring population sweep. The path needs a time source, an offset and its own first element. An immediate end prevents the delayed action from running as soon as the record qualifies. This workspace uses whole calendar days and an explicit local execution date.
A pending path must remain tied to the current source record. Changing the date cancels the old job and schedules the new date; leaving the entry population cancels pending work. An unrelated edit must not create another reminder. At execution time the checker reads the current record and its source date again. Test before the due day, on the due day, after cancellation and after a repeated execution.