Backstop for missed Utila webhooks, and the initial backfill. Each run walks every vault named in its `vaultIds` argument, oldest-first, creating any transactions that are missing, then asserts each feed was drained by comparing Utila's total against the stored count — a mismatch fails the run rather than leaving balances quietly wrong. Existing rows are never duplicated. One schedule covers every vault its `vaultIds` names, sourced from this environment's Utila vault configuration (prod: operating and custody).
This schedule doesn't exist in Temporal. It never runs.
{
"vaultIds": [
"6e3ef89edac6"
]
}Showing runs Temporal still retains.
| Started | Scheduled for | Outcome | Workflow id |
|---|---|---|---|
| No schedule; nothing has run yet. | |||