Acknowledged Release Initiation Escalation
Acknowledged Release Initiation Escalation
Overview
Once a deposit release has been acknowledged by all parties, it must be formally initiated through the deposit scheme within a reasonable timeframe. The Acknowledged Release Initiation Escalation workflow ensures that no release stalls at this stage by automatically alerting organisation admins when action is overdue.
How It Works
Trigger
The workflow runs on a daily schedule at 08:00 UTC (0 8 * * *).
Logic
On each run, the system performs a sweep of all deposit releases matching the following condition:
status = 'acknowledged'
AND acknowledgedAt + 7 days <= today
Any release meeting these criteria is considered overdue for initiation and triggers an escalation.
Escalation Action
For each overdue release, an escalation notification is sent to all administrators of the associated organisation. The notification communicates that the deposit release has been acknowledged but has not yet been initiated through the deposit scheme, and that action is required.
Entities Involved
| Entity | Role |
|---|---|
depositReleases | Source records evaluated by the sweep |
notifications | Delivery mechanism for escalation alerts |
organizations | Determines which admins receive the notification |
Timeline Reference
Day 0 — Release acknowledged (status set to 'acknowledged', acknowledgedAt recorded)
Day 1–6 — No escalation (within the 7-day window)
Day 7+ — Escalation triggered; org admins notified daily until resolved
Who Receives Escalation Notifications?
Escalations are sent to organisation admins — users with an admin role within the organisation that owns the deposit release. Agents and tenants are not notified at this escalation stage.
Resolving an Escalation
To stop receiving escalation notifications for a given release, an admin must initiate the deposit release through the deposit scheme. Once the status transitions out of acknowledged, the release will no longer be included in future sweeps.