Schedule identity for the Utila vault transaction sync.
Mastered by the admin dashboard, never by temporal-worker's
scheduledWorkflows.ts — the same "dashboard is sole master from day one"
choice already made for the Victor and RouteFusion transaction syncs. An
operator's cadence then survives a worker deploy, because nothing re-upserts
the schedule on boot.
These constants live here rather than in the dashboard so the schedule id and
the workflow type have exactly one definition each. The dashboard registry
imports them; a rename is then a compile error rather than a schedule that
silently starts nothing.
Schedule identity for the Utila vault transaction sync.
Mastered by the admin dashboard, never by
temporal-worker'sscheduledWorkflows.ts— the same "dashboard is sole master from day one" choice already made for the Victor and RouteFusion transaction syncs. An operator's cadence then survives a worker deploy, because nothing re-upserts the schedule on boot.These constants live here rather than in the dashboard so the schedule id and the workflow type have exactly one definition each. The dashboard registry imports them; a rename is then a compile error rather than a schedule that silently starts nothing.