← Power BI DesktopCONTENT HISTORY

Update to Power BI Desktop

Snapshot Sep 30, 2026 · 23:15 UTC · version 3.0.0+codex.20260829143201

Collection source: not recorded for this historical snapshot.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "name": "powerbi-autonomous-exception-management",
  "description": "Use when turning autonomous Power BI planning deviations into managed exceptions, including revenue gaps, risky backlog, unrealistic targets, biased models, sparse segments, owner hints, status, escalation, and closure evidence.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 151
    }
  ],
  "skill_md_contents": "---\r\nname: powerbi-autonomous-exception-management\r\ndescription: Use when turning autonomous Power BI planning deviations into managed exceptions, including revenue gaps, risky backlog, unrealistic targets, biased models, sparse segments, owner hints, status, escalation, and closure evidence.\r\n---\r\n\r\n# Power BI Autonomous Exception Management\r\n\r\nUse this skill when every planning deviation should become a traceable exception rather than a dashboard comment.\r\n\r\n## Exception types\r\n\r\n- `budget_gap`\r\n- `roll_gap`\r\n- `backlog_at_risk`\r\n- `delivery_risk`\r\n- `model_biased`\r\n- `sparse_segment`\r\n- `target_infeasible`\r\n- `human_override_required`\r\n- `data_quality_blocker`\r\n\r\n## Workflow\r\n\r\n1. Detect exceptions from forecast, quality, scenario, constraint, and action outputs.\r\n2. Deduplicate by month, customer, product, issue type, and root cause.\r\n3. Assign severity from revenue impact, confidence, urgency, and controllability.\r\n4. Suggest owner hints from customer hierarchy, sales group, product line, or region.\r\n5. Track status and closure evidence.\r\n\r\n## Required outputs\r\n\r\n- `exception_id`\r\n- `forecast_month`\r\n- `exception_type`\r\n- `customer`\r\n- `product`\r\n- `revenue_impact`\r\n- `severity`\r\n- `owner_hint`\r\n- `status`\r\n- `next_action`\r\n- `evidence`\r\n\r\n## Guardrails\r\n\r\n- Every severe exception needs an action, owner hint, or explicit reason to defer.\r\n- Do not close exceptions automatically without actuals, owner response, or rule-based evidence.\r\n"
}

SHA-256: f639c251b96ccd7c0a6a2c0cc184ccdf769941b022c48a093226d98c812c6422