Use “Advance a job stage” in Recued. CAS-updates one Records job and then convergently creates the progress event watched by the notification recipe. Two actors holding the same revision cannot both win.
Advance a job stage
Use “Advance a job stage” in Recued. CAS-updates one Records job and then convergently creates the progress event watched by the notification recipe. Two actors holding the same revision cannot both win.
Complete workflow
Job Status Board
9 pinned recipes
Use Job Status Board in Recued for reception, intake, records, and local first. It includes 12 built-in actions and 7 ready-to-run workflows. Actions that change data use Recued's approval controls.
You are viewing one recipe in this workflow. Installing it opens the complete pack so its other recipes and background automations arrive together.
Use “Open a job from an intake response” in Recued. Turns one accepted Reception response into one deterministic Records job and one deterministic opened event. Retrying after either create boundary converges on the same two rows; visitor text stays in PII-labelled owner-local fields.
Use “Attach a status page to a job” in Recued. Reads one Records job and CAS-upserts the owner-minted status URL without changing its other fields.
Use “List the job board” in Recued. Searches Records by status, sorts by latest update, counts the exact result set, re-reads the page with getmany, and renders detail actions. The board pages through the result set and re-filters in place from its own declared variables.
Use “List reclaimable jobs” in Recued. It provides a read-only view of archived jobs, oldest touched first, with how long each has been sitting and a per-row reclaim action.
Use “Reclaim a closed job” in Recued. Changes remain behind Recued's approval controls.
Show all 9 recipes
Use “Close a job” in Recued. CAS-closes one Records job, archives it from the active board, and creates one deterministic close event for the notification watcher.
Use “Notify a customer about job progress” in Recued. Records watcher for committed jobevent rows. It re-reads the pointer by id and uses the durable event id as the mail reconciliation key, so delivery retries converge without claiming provider-level exactly once.
Use “Records runtime” in Recued. It helps you complete this workflow using the connections and settings you choose.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Data fetch
job
?
▼
Process (13 steps)
stage
trim
Trim whitespace from setting new stage
line
trim
Trim whitespace from setting customer line
line_bounded_value
truncate
Truncate line to a max length
line_bounded
compare
Check if line equals line bounded value
inputs_valid
all
Check if all conditions are true
inputs_guard
guard
Stop if inputs valid equals
already_applied
all
Check if all conditions are true
job_update
?
skip: step.already_applied equal true
effective_job
coalesce
Use the first available value from: job update record, job record
event_id
template
Generate text from a template
job_ref
template
Generate text from a template
event_create
?
card
to_summary
Format results as a summary card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
job id
setting
=
progress
setting
=
50
new stage
setting
=
in_progress
customer line
setting
=
Your job is now in progress.