Insights and alerts ​

Use these surfaces to find four useful outcomes in captured activity:

  • Improving result: Client-review time is improving across the launch queue.
  • Attention item: Three launch deliverables are waiting for client approval.
  • Repeated pattern: A recurring handoff or queue path is worth investigating.
  • Schema issue: One deliverable is missing a current status; review it and assign the correct status.

Alerts ​

Alerts identify items that may need review. An alert shows its title, summary, and severity; use Activity for the captured evidence behind an important conclusion. Dismissing an alert removes it from the open-alert view; it does not repair the underlying condition.

This alert card identifies three launch deliverables waiting for client approval for more than five days.

For detailed source activity, open Activity. A later observation can produce another alert if the condition remains relevant.

Metric trends show movement in a saved measurement across comparison windows. Open the related metric for its definition, history, time range, and supporting activity when available.

See Metrics for reading metric trends and Metric definitions for editing and comparison limits.

Repeated work patterns ​

Repeated work patterns summarize paths and variants found in captured activity for the selected scope. They are prompts for investigation, not workflows that every record must follow. Work outside the selected scope or capture history is not represented.

The dashboard's Processes surface shows the available paths and variants. For path and grouping details, see the advanced process reference.

Schema validations ​

Schema validations appear on the Alerts page alongside Open alerts. They show deterministic findings about captured tables, fields, or values. A finding can show its severity, message, affected table or field, suggested fix, and available actions such as Autofix, Show history, Open table, or Dismiss. Positive trends belong in Open alerts or Insights, not in Schema validations.

Schema validations flag Deliverables.Status because one deliverable is missing a current status and suggests assigning the correct status.

Schema validations flag structures or values that may affect interpretation. When no findings are present, the surface reports “No schema issues.”

For reports that combine several sources into a briefing, see Reports.

Interpret results in context

These surfaces summarize captured activity within your selected scope and history. A connection or processing delay, short history, changed scope, or missing source data can make the newest period incomplete; use Activity and its Source details view to verify important conclusions.