Schedule identity for the Utila vault transaction sync.
Mastered by the admin dashboard: temporal-worker creates the schedule when
it is missing and never re-upserts it, so an operator's cadence survives a
worker deploy.
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:
temporal-workercreates the schedule when it is missing and never re-upserts it, so an operator's cadence survives a worker deploy.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.