Trigger: Record Overdue

The Record Overdue trigger (record.overdue) fires a workflow when a record with a due date — a task, a board item — passes it without being marked complete. This isn't an instant user action: it's fed by a scheduled sweep that periodically checks records with a configured deadline (the same mechanism behind boards:detect-overdue).

When it fires

It fires during the periodic overdue sweep, the first time it detects the record's due date has passed and it's still not completed.

Requirements

• Records with a configured due date (in Boards or the relevant Projects/CRM module).

Trigger configuration

• Record type: leave blank for any type, or set one (task, item, deal) to narrow the trigger.

Available variables

• $record.object_type — Type of the overdue record
• $record.object_id — Record ID
• $record.workspace_id — Record's workspace

Example

A workflow triggered by record.overdue with Record type = task: when a project task passes its deadline without being completed, the workflow reassigns it to the team lead and posts a Team message tagging them to pick it up as a priority.

Tips

• Consider semantic triggers like deal.no_activity if your specific case is stalled CRM deals, instead of the generic record.overdue.
• This trigger depends on an internal cron — if your workspace's sweep has a delay, firing can lag until the next scheduled cycle rather than happening at the exact due moment.

Troubleshooting

If an overdue record never fires the workflow, confirm it actually has a due date configured (not just a creation date) and that the corresponding sweep is enabled in the workspace.