Recued
Menu
← Back to recipes

Handle Codex Failure

by recued-core v1 21 views

Use “Handle Codex Failure” in Recued. It carries out the named workflow using the connections and settings you choose.

How it works 8 steps

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

Process (8 steps)
◆ listing core.storage.shared.list
List storage shared
■ rows filter
Filter by condition
⚠ guard_rows guard
Stop if rows is empty
■ now date_add
Add 0 days to
◆ notify core.mail.send
Send mail
◆ mark_handled core.storage.shared.write
Write storage shared
■ handled_count count
Count items in rows
■ card to_summary
Format results as a summary card
▼
Output
summary card
Settings 2 configurable

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

notify to setting = —
sender mail instance setting =

Uses (3 operations)

Shared store List storage shared core.storage.shared.list
Mail Send mail core.mail.send
Shared store Write storage shared core.storage.shared.write

Trust & control

What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.

Permissions it requires

Mail send
Declared by the recipe — Recued grants these at install, where you review them before approving.

What it's allowed to do

Read Shared store core.storage.shared.list read-only
Write Mail core.mail.send external change
Write Shared store core.storage.shared.write external change

Data it touches

SurfacesShared storeMail
Warehousedata.shared

About

Tags

codexpipelined-179handlerfailurestallnotify

Details

8 steps 2 configurable settings recipe_id: handle-codex-failure