> ## Documentation Index > Fetch the complete documentation index at: https://docs.meetdoris.com/llms.txt > Use this file to discover all available pages before exploring further. # Commitment overdue > Runs when an open commitment passes its due date. **Event id:** `commitment.overdue` Fires from the daily sweep that moves open commitments into an overdue state. ## When it fires Once a day, Doris checks every open commitment against its due date and marks the ones that have passed it. Each commitment that flips to overdue fires this trigger, once. ## What the flow receives * **Commitment** — The promise, as captured * **Due date** — The date it was due * **Days overdue** — How far past the due date it now is * **Deal** — The deal it belongs to, expandable into full deal context ## Good uses * Tell the rep the same morning that something they promised has slipped * Escalate to a manager when a commitment on a large deal goes overdue * Add an overdue count to a deal's CRM record so it shows in pipeline reviews * Post overdue buyer commitments into a channel as an early stall signal ## Things to know * It fires once, when the commitment first becomes overdue. It does not fire again each day it stays overdue. If you want a running list of everything outstanding, build that on a [Daily schedule](/features/triggers/daily-schedule) instead. * Commitments with no due date never become overdue and never fire this. A flow on [Commitment created](/features/triggers/commitment-created) that flags undated commitments is the companion to this one. * The sweep runs daily, so the trigger fires on the day after the due date, not at the exact hour it lapsed. * Doris can close a commitment on its own when it sees the evidence, which stops it becoming overdue. Overdue buyer commitments are one of the earliest signs a deal is stalling. A flow here catches it before it shows up in the forecast.