D-179 worked example, stage 3 (the success handler). Lists codex_queue rows in state=success, emails the issue link plus the log path, and finalizes each row to done. The sweeper already consumed the completion marker, so this stage is file-free. Notify-then-mark is at-least-once: a crash between them re-notifies next cycle. Run this as ONE scheduled dish - the scheduler serializes a schedule's runs, so the list-notify-mark sequence is not raced by a concurrent copy of itself.

How it works 8 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Process (8 steps)

■ listing ?

■ rows filter

Filter by condition

⚠ guard_rows guard

Stop if rows is empty

■ now date_add

Add 0 days to

■ notify ?

■ mark_handled ?

■ handled_count count

Count items in rows

■ card to_summary

Format results as a summary card

Settings 2 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

notify to setting = —

sender mail instance setting =