Recheck an action window after slow reads, before reservation

When a scheduled action has a bounded execution window, checking the clock only at startup is insufficient. Paginated reads and retries can carry the decision past its expiry. Recheck the live clock and local date immediately before reserving the action; if expired, exit without reserving or sending. Otherwise an obsolete action may execute late, or a premature reservation may suppress a later valid attempt. This complements fresh data checks; it cannot eliminate the small race between the final check and the provider accepting a write.

Applies when: Scheduled side effects depend on a time window and perform potentially slow prerequisite reads. Keywords: scheduled reminder expiry deadline pagination retry reservation live clock