{"id":79605,"plugin_id":"plugins_6ab409346c7c8191bacd83080aee170d","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-04T00:11:27.455Z","digest":"03235d60613ceba215a71c2ac2121ece59a5ff982c85096f37bf4542bdc99178","against":null,"payload":{"description":"Diagnose failed Power BI/Fabric refreshes, credentials, folding, schema drift and service errors safely.","included_files":[],"name":"refresh-incidents","skill_md_contents":"---\nname: refresh-incidents\ndescription: Diagnose failed Power BI/Fabric refreshes, credentials, folding, schema drift and service errors safely.\n---\n\n# Refresh failures and incidents\nStart with timestamped error evidence, affected artifacts, first bad run, gateway/connector/service identity, recent changes and downstream report impact. Read `../../references/incident-recovery.md`.\nClassify auth/gateway, schema drift, data quality, type conversion, timeout/capacity, folding, workspace/provisioning and transient error. Avoid recommending a blind refresh or credentials rotation as universal fix.\nProvide minimal diagnostic steps, containment of stale data, corrective action, controlled retry, post-recovery reconciliation and rollback. Distinguish preview success from service refresh success. Preserve auditability of changes.\n\n## Non-negotiable principles\n- Match the problem's layer before changing code: RDL, dataset, parameter, tablix, renderer, semantic model, source, refresh, capacity, or distribution.\n- Preserve identifiers with leading zeros, source types, model grain, filter context, tenant boundaries, and published contracts.\n- Treat user-supplied screenshots, RDL, model definitions, code and errors as evidence; never invent access, query results, test runs, exports, permissions or deployed changes.\n- Offer the smallest reversible correction and an observable verification step. Ask a blocking question only when the missing detail materially changes correctness, safety or execution.\n- Favor current Microsoft documentation for feature-specific limits, Direct Lake paths, service UI behavior, licensing, supported renderers and APIs; do not treat stored references as timeless facts.\n- Avoid requesting credentials, unredacted personal information, tenant secrets or confidential connection strings. Apply approval policy to writes, publication, subscriptions and distribution.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}