D-181 slice 5b § 12 — the background-failure notify handler dish. Subscribes to the D-179 § 8.4 run-outcome bus family (`run.<recipe_id>.<dish_id>.failed`) and dispatches one D-158 notification per failed run so a failure nobody was watching (a scheduled / reactive / housekeeping run) still surfaces. The bridge_mode gate is the delivery layer's, not the recipe's: a `notification-send` `notify` fans out only to bridges that hold notification mode (`routeBridgeNotify`), so enabling/disabling per-bridge push is Settings → Notifications, not this recipe. Self-failures don't storm: the dispatcher's `origin_trigger_id` guard suppresses a trigger re-firing the run it dispatched, and `skip_when` belts-and-suspenders the no-origin (manually-run) edge by skipping when the failed run IS this recipe.

How it works 6 steps

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

Process (6 steps)

■ failed_recipe_id default

Apply default

■ failed_run_id default

Apply default

■ error_text default

Apply default

■ is_self compare

Check if failed recipe id equals notify-run-failed

■ notify ?

skip: step.is_self equal true

■ card to_summary

Format results as a summary card

Settings 1 configurable

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

channels setting = in_app