trigger
How it's scheduled
Chained — no clock of its own
This runs after its source-data load completes, as a follow-on stage rather than on an independent schedule.
| Scheduled task | Cadence | Server | State | Coordination |
|---|---|---|---|---|
\MDC\Test - ECP - TestWorkbox - 2 | on demand / chained | prod-db-3 | enabled | standalone |
\MDC\Test - ECP - TestWorkbox - 3 | on demand / chained | prod-db-3 | enabled | standalone |
\Test\Test - Jobs to Run After | on demand / chained | prod-db-3 | enabled | yields to \Test\RunOneHour, \Test\RunTwoHours |
shape
Against the canonical Flow spine
Every Flow pipeline is a variation on one shape. Lit stages are the ones this pipeline runs; the labels match the capability lens.
Ingest
Batch / file feed
Eligibility & benefits
Estimate
Letters
Work queue & sync
task tree
What the pipeline runs
Tasks in order, each with what it does — typed stepsfrom the MDClarity task docs (click to open the reference), sub-jobsyou can expand inline (▶) to reveal their own tasks, and SQL steps summarized by Gemini (✨). Every step shows the tables it writes/reads and which earlier step it feeds from(sqlglot lineage).
other
Test-Workbox
1 tasks · ECP
sub-job / Flow action SQL / native step▶ expand a sub-job inline · ↗ open it as its own page · a typed step opens its doc
- ExecuteSqlsql
test_workbox__executesql.sql· readsAccount