Overdue commitments

A commitment is easier to keep when the missed date remains visible. Overdue commitments gives a team a short list of overdue work to review with the people responsible.

Try the report

Enable Overdue commitments in Plugins, then choose Run report. It uses the workspace’s existing tasks and needs no plugin-specific credentials. The plugin starts disabled. Use an authorized workspace, or explore Plugins in the fictional demo.

A fictional task to send a project summary was due yesterday. A second task is already complete. The pending task appears in the report; the completed task does not. Open the source task to review or change the next step.

Pending or snoozed tasks with a due date before the current UTC date qualify. Tasks due today and completed tasks are excluded.

Read the result

Each finding is a reason to inspect its source. Check the inspected-record count and any truncation indication before drawing a conclusion. Each source is limited to 100 records, the combined input to 64 KiB, and displayed findings to 20. An empty result means no matches in that snapshot; it does not certify the entire business.

The report is read-only and deterministic. It neither changes business records nor contacts anyone. Its AI/MCP tool is run_commitment_watch; the host checks whether the plugin is enabled when it runs. The report needs no write approval and makes no model request. Hosting and database usage still apply, and an AI conversation around the report can incur model charges.

What this example teaches you to build

Turn a precise business rule into an inspectable report. This pattern can support other deadline reviews once the relevant records and permissions exist. The current report does not reschedule tasks or send reminders.

Start with the report source and its module manifest. The report code receives declared fields inside the shared isolate; the host supplies access and records the result. Reuse that boundary when changing the logic.

Disable or recover

Turn the plugin off in Plugins to stop new evaluations. Source records and historical receipts remain. For missing-source or access errors, check the workspace's source registration and permissions, correct them, then rerun. For truncated results, inspect the source records rather than assuming the omitted records are clear. Repeating a report does not create duplicate tasks or messages.

The developer guide links the source contracts and controlled tests, including npm run test:report-plugins. Those fixtures exercise the report behavior; they do not verify every installation's data or provider connections.