Watch A Deletion Through Its Waiting Period
What It Does
Watch recorded notice times and eligibility without keeping a function running. The watcher checks its current request reference on each task. Due-notice selection excludes recorded delivered or suppressed outcomes, but sends can repeat before persistence.
The Flow
When Something Fails
Retry read errors under notice-task policy. No request mutation is required. Throw for per-notice failures while fast retries remain; recipient setup can fail earlier. Provider acceptance can precede the recorded outcome and cause duplicate delivery. Return a bounded wake result rather than blocking in the function. No destructive decision is made here. Execution failure or the one-year timeout stops the watcher. The request can remain scheduled or held without a live watcher. Unexpected task failure is recorded; job recovery needs schedule resume. The request retains its standing when the watcher stops.
Open Design Questions
Recipient setup and notice-delivery failures have different persistence boundaries. The one-year execution limit requires operational recovery for longer waits.