This trigger is different from the others because it is time-based rather than save-based. A nightly job checks projects and tasks against the configured threshold and then fires the automation when the overdue condition is reached.

Use this trigger when the important question is not whether someone changed a record, but whether work has stayed late long enough to need attention. It is well suited for reminder emails, escalation workflows, dashboard follow-up, or recurring comments that keep overdue work visible until someone acts on it.

• Entity Type chooses whether the trigger walks projects, tasks, or both.
• Initial Threshold (Days) determines when the first firing happens relative to the due date.
• Repeat Every (Days) controls whether the trigger fires only once or keeps firing on a cadence after the threshold is reached.
• For tasks, the optional Project Type filter evaluates the parent project's type.
• Merge fields include the overdue entity, whether it was a project or task, the number of days overdue, and the project type context.

The most important configuration decision is whether you want a one-time nudge or an ongoing cadence. Initial Threshold decides when the first trigger happens. Repeat Every decides whether it stops there or continues on a schedule such as daily or weekly until the work is resolved.

Merge Fields

• Entity is the overdue project or task.
• EntityTypeName tells you whether the fired item was a Project or a Task.
• NumberOfDaysOverdue is the calendar-day count past the due date at the moment the trigger fired.
• ProjectType is the project's type, or for tasks the parent project's type.