← back to indexservice_hold_trigger

Service hold trigger risk 4 · highAR & financereflexion on

workflow_type: service_hold_trigger · owner: — · contract v2

Customer crosses AR threshold + days criteria. Flag for service hold: customer flag, sales rep notification, customer-facing notice, NS order block.

0 · Visual flow archify workflow graph (6 lanes: trigger → context → HITL → fan-out → post → verify)

Workflow flow
01 / Trigger 02 / Context + preconditions 03 / HITL gate (Mike approves) 04 / Fan-out cascade 05 / Post actions (log_run + reflexion + events) 06 / Verify (SQL / R2 / HTTP checks) How this workflow gets kicked off. Could be a chat-tool invocation, a cron tick, an inbound event (e.g. price.changed), or Mike clicking 'execute' from an admin page. TRIGGER kind: event sources: ar_aging_tick_threshold, manual invoker: Mike (single-admin) risk_level: 4i Manual Mike invokes risk 4 Before deciding anything, pull related data from D1 (the local mirror of NetSuite). Each query loads a slice of the entity's current state so the AI and Mike can review before any writes happen. LOAD CONTEXT (D1 queries before fan-out) customer: SELECT * FROM customers WHERE id=? open_sos: SELECT COUNT(*) AS n, SUM(foreigntotal) AS total FROM transactions WHERE entity… prior_holds: SELECT COUNT(*) FROM auto_decisions WHERE entity_type='customer' AND entity_id=…i Load context 3 D1 queries Safety checks that must pass before any writes. 'block' severity halts the run; 'warn' surfaces a warning but continues. Without these, a bad input could cascade into NetSuite. PRECONDITIONS (checked before fan-out) [block] customer_active: customer.isinactive != 'T' [warn] reasonable_threshold: days_overdue >= 60 AND ar_balance >= 10000i Preconditions 2 checks The HITL (Human-In-The-Loop) gate. The workflow stages a proposed_action and waits for Mike to approve in /proposed-actions.html. Only fires when risk_level >= 3. This is the invariant: no NS write happens without Mike's go-ahead. HITL GATE (Mike approves before fan-out) action_type: workflow_service_hold_trigger entity_ref: workflow:service_hold_trigger:run_<run_id> approver: mike (single-admin) risk_gate: >= 3 (this workflow = 4) approval window: typical <= 60 min envelope: proposed_actions row staged by runneri Mike approves stage_proposed_action risk ≥ 3 gate Write to the local D1 mirror (the read-side cache of NetSuite). Used for derived data and platform state. STUB today - per-tool d1_write logic lives in chat_tools/impls.ts. FAN-OUT #flag_customer -> D1: customers kind: d1_write op: UPDATE customers SET entitystatus='hold', last_modified=now WHERE id=? status: REAL (src/lib/workflow_runner.ts)i flag_customer d1_write STUB Draft an email and stage it as a proposed_action for Mike's review. The email is NOT sent - only drafted + queued. STUB today. FAN-OUT #notify_sales_rep -> email draft kind: hitl_email_draft tool: propose_email_to_customer status: STUB (src/lib/workflow_runner.ts)i notify_sales_rep hitl_email_draft STUB Draft an email and stage it as a proposed_action for Mike's review. The email is NOT sent - only drafted + queued. STUB today. FAN-OUT #draft_customer_notice -> email draft kind: hitl_email_draft tool: propose_email_to_customer status: STUB (src/lib/workflow_runner.ts)i draft_customer_notice hitl_email_draft STUB Pushes a write back to NetSuite via the NS_PUSH_QUEUE. The push is staged in ns_pending_pushes first and only flips to 'applied' after NS confirms. STUB today - the runner logs intent but doesn't enqueue yet. FAN-OUT #ns_order_block -> NS_PUSH_QUEUE: customer kind: ns_push queue: NS_PUSH_QUEUE record_type: customer status: REAL (src/lib/workflow_runner.ts)i ns_order_block ns_push STUB Always-runs at the end of every workflow execution: writes a row to workflow_run_log with status, duration, step counts, and errors. Real implementation. POST ACTION: log_run -> D1: workflow_run_log fields: run_id, workflow_type, status, started_at, completed_at, summary_json source: runner automatic (always)i log_run workflow_run_log REAL Writes an entry to reflexion_log so the AI 'remembers' what happened. Only fires if the contract has reflexion_enabled=1. Future workflows can search this log for prior context. Real implementation. POST ACTION: reflexion -> D1: reflexion_log tags: service_hold_trigger reflexion_enabled: True fields: run_id, narrative, tags source: runner automatic (when reflexion_enabled=1)i reflexion reflexion_log REAL Fires a workflow.completed / workflow.partial / workflow.failed event into the event ledger so downstream subscriptions can react. Uses an idempotency_key so producer retries collapse. Real implementation (R564). POST ACTION: event -> Event ledger (recordEvent) types: workflow.completed | workflow.partial | workflow.failed idempotency_key per run_id source: runner automatici event workflow.completed REAL A post-execution sanity check. The runner stages this with status='pending'; the verify-scheduler cron (every :08 and :38 hourly) wakes up after the configured window (e.g. +24h) and executes the sql_check, then flips status to pass/fail/timeout. Real implementation (R564). VERIFY: hold_applied_d1 window: 5s sql_check: SELECT entitystatus FROM customers WHERE id=? scheduler: verify cron @ :08/:38 (R563) result row: workflow_verify_resultsi hold_applied_d1 ≤60m A post-execution sanity check. The runner stages this with status='pending'; the verify-scheduler cron (every :08 and :38 hourly) wakes up after the configured window (e.g. +24h) and executes the sql_check, then flips status to pass/fail/timeout. Real implementation (R564). VERIFY: hold_applied_ns window: 15m scheduler: verify cron @ :08/:38 (R563) result row: workflow_verify_resultsi hold_applied_ns ≤60m Legend User UI Agent logic Policy Tool action Context / trace
Open standalone archify diagram (export PNG / SVG) →

1 · Trigger FIRES WHEN…

kind
event
sources
["ar_aging_tick_threshold","manual"]

2 · Inputs required

namerequiredtype / hint
customer_idrequired—
ar_balancerequired—
days_overduerequired—
reasonrequired—

3 · Context loaded D1 queries run before fan-out

name
customer
tables
customers
SELECT
  *
  FROM customers
  WHERE id=?
name
open_sos
tables
transactions
SELECT
  COUNT(*) AS n, SUM(foreigntotal) AS total
  FROM transactions
  WHERE entity=?
  AND type='SalesOrd'
  AND status NOT IN ('closed','cancelled')
name
prior_holds
tables
auto_decisions
SELECT
  COUNT(*)
  FROM auto_decisions
  WHERE entity_type='customer'
  AND entity_id=?
  AND decision_type='service_hold'

4 · Preconditions checked before any fan-out

checkruleseverity
customer_activecustomer.isinactive != 'T'block
reasonable_thresholddays_overdue >= 60 AND ar_balance >= 10000warn

5 · HITL gate

Risk level 4 ≥ 3 — runner stages a proposed_actions row before fan-out runs. Mike must approve in proposed-actions.html before any side-effect step executes (real or stub).

action_type
workflow_service_hold_trigger (proposal envelope)
entity_ref
workflow:service_hold_trigger:run_<run_id>
approver
mike (single-admin)

6 · Fan-out targets 4 total · 0 real · 4 stub

#1flag_customer d1_write STUB

operations
["UPDATE customers SET entitystatus='hold', last_modified=now WHERE id=?"]
stub — not yet implemented in src/lib/workflow_runner.ts (kind d1_write hits the placeholder branch at line ~340 and emits step status 'stub'). Documented intent only.

#2notify_sales_rep hitl_email_draft STUB

tool
propose_email_to_customer
target
sales_rep
stub — not yet implemented in src/lib/workflow_runner.ts (kind hitl_email_draft hits the placeholder branch at line ~340 and emits step status 'stub'). Documented intent only.

#3draft_customer_notice hitl_email_draft STUB

tool
propose_email_to_customer
target
customer
stub — not yet implemented in src/lib/workflow_runner.ts (kind hitl_email_draft hits the placeholder branch at line ~340 and emits step status 'stub'). Documented intent only.

#4ns_order_block ns_push STUB

NS record_type
customer
queue
NS_PUSH_QUEUE
payload
{credit_hold:true}
stub — not yet implemented in src/lib/workflow_runner.ts (kind ns_push hits the placeholder branch at line ~340 and emits step status 'stub'). Documented intent only.

7 · Post actions declared + runner-automatic

idactionsource
runner_log_runINSERT into workflow_run_log (run_id, workflow_type, status, started_at, completed_at, summary_json)runner automatic
runner_reflexionINSERT into reflexion_log (tags=service_hold_trigger, run_id, narrative)runner automatic (reflexion_enabled=1)
log_runINSERT workflow_runsdeclared in contract
reflexionINSERT reflexion_log with tags=service_hold,customer:?declared in contract
auto_decisionsINSERT auto_decisions rowdeclared in contract

8 · Verify checks written to workflow_verify_results (pending — verify cron not yet wired)

name
hold_applied_d1
SELECT
  entitystatus
  FROM customers
  WHERE id=?
name
hold_applied_ns
when_to_run
15 min after run

9 · Retry policy

max_attempts
3
backoff
exponential
base_ms
2000
max_ms
30000
alert_on_final_failure
true

10 · What changes when this workflow runs aggregated side effects

systemtable / resourceactionstatussource
D1workflow_run_logINSERT (run summary)REALrunner automatic
D1reflexion_logINSERT (tags=service_hold_trigger)REALrunner automatic
Eventworkflow.completed (or workflow.failed)fireREALrunner automatic
D1workflow_verify_resultsINSERT pending × 2REALrunner verify staging
D1proposed_actionsINSERT (HITL gate envelope)REALrunner HITL gate
D1unknownwriteSTUBfan-out #1 (flag_customer)
D1proposed_actionsINSERT (email draft via propose_email_to_customer)STUBfan-out #2 (notify_sales_rep)
D1proposed_actionsINSERT (email draft via propose_email_to_customer)STUBfan-out #3 (draft_customer_notice)
NetSuite (via NS_PUSH_QUEUE)customerpushSTUBfan-out #4 (ns_order_block)