Skip to content
Recued
Menu
← Back to recipes

Adobe Sign agreement closure watcher timeout

by recued-core v1

Low-frequency timeout role for recued-core/adobe-sign-agreement-closure. It moves a bounded batch of expired rows from active to timed_out, deletes the active copy only after the durable timeout write succeeds, and notifies the owner once per batch.

Complete workflow

Workflow pack for Recued-sent Adobe Sign agreements. It composes the Adobe Sign capability pack with a closure ledger: create one agreement through the existing Adobe Sign approval gate, persist only the agreement/library-document/workflow linkage in data.shared when the agreement is sent with IN_PROCESS, and let a scheduled watcher re-read that exact agreement until Adobe Sign reports a role-specific completion status such as signed/approved/delivered/accepted/form_filled, or an exception status such as aborted/cancelled/expired/archived. This pack does not duplicate Adobe Sign reminders, participant notifications, expiration settings, webhook administration, agreement status dashboards, cancellation flows, or MegaSign/bulk sends; it adds Recued-visible closure state for agreements Recued sent.

You are viewing one recipe in this workflow. Installing it opens the complete pack so its other recipes and background automations arrive together.

Adobe Sign agreement closure watcher timeout
This recipe Background automation

Low-frequency timeout role for recued-core/adobe-sign-agreement-closure. It moves a bounded batch of expired rows from active to timed_out, deletes the active copy only after the durable timeout write succeeds, and notifies the owner once per batch.

adobe-signwatchertimeoutowner-review
by recued-core pinned v1

Workflow origin for the Adobe Sign agreement closure loop. It reads the current user and one library document for context, creates one agreement through recued-core.adobe-sign.agreement.create, and when the owner sends the agreement with initial state IN_PROCESS it seeds durable data.shared closure state for adobe-sign-agreement-closure-watcher plus links the agreement back to its library document and optional workflow. It does not send reminders, cancel agreements, update notes, upload transient documents, download binaries, open signing URLs, configure webhooks, start MegaSign/bulk sends, mutate templates, or call arbitrary Adobe Sign endpoints.

adobe-signacrobat-signesignatureagreement-create
by recued-core pinned v1
Adobe Sign agreement closure watcher
Background automation

Scheduled adopter for Adobe Sign agreement closure rows seeded by send-adobe-sign-agreement-with-closure. It lists only Recued-originated agreement watches, re-reads a bounded batch of Adobe Sign agreement, and closes or flags the shared row when Adobe Sign reports a configured terminal status. It can notify the owner on completion or exception status, but it never creates agreements, sends reminders, cancels agreements, updates notes, downloads binaries, opens signing URLs, configures webhooks, starts MegaSign/bulk sends, mutates templates, or calls arbitrary Adobe Sign endpoints.

adobe-signacrobat-signesignatureagreement
by recued-core pinned v1

Read-only Adobe Sign agreement brief. It reads one agreement, its reminders, and the API user's latest note through recued-core.adobe-sign, then asks the AI summarizer for lifecycle state, participant status, reminder history, notes, expiration risk, and concrete next steps. It never creates agreements, sends reminders, cancels, updates notes, downloads binaries, opens signing URLs, or calls arbitrary Adobe Sign endpoints.

adobe-signacrobat-signesignatureagreement-review
by recued-core pinned v1

Owner-visible list/close role for recued-core/adobe-sign-agreement-closure. It lists bounded active, timed-out, and closed rows. Supplying a timed-out or closed key deletes only that exact terminal row; active watches cannot be deleted here.

adobe-signwatcherreviewclose
by recued-core pinned v1
View pack details, dependencies, and permissions →
How it works 16 steps

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

Data fetch
active_watches ?
Process (15 steps)
now date_add
Add 0 minutes to
rows_with_timeout filter
Filter by condition
timeout_checks is_past
Check if is in the past
expired_checks filter
Filter by condition
expired_rows map
Extract from each item
timeout_rows slice
Take a subset of
timeout_count count
Count items in timeout rows
timeout_keys replace
Replace text in item key
timeout_values merge
Combine objects together
write_timed_out ?
delete_active ?
skip: item.result.ok not_equal true
moved_rows filter
Filter by condition
moved_count count
Count items in moved rows
notify_owner ?
skip: step.moved_rows is_empty
summary to_summary
Format results as a summary card
Settings 2 configurable

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

channels setting = in_app
batch limit setting = 25

Trust & control

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

Where it runs

Device + server Runs on your device (browser) or your server.

Permissions it requires

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

Data it touches

Warehousedata.shared

About

Tags

adobe-sign watchertimeoutowner-reviewclosed-looprole:timeoutbundle:adobe-sign-agreement-closure

Details

16 steps 2 configurable settings recipe_id: timeout-adobe-sign-agreement-closure-watches