POWER BI REPAIR BRIEF

Use with your administrator, developer or Turing BI.
Keep passwords, gateway recovery keys, report files and customer records out of
this brief. Arrange access and sample data through an agreed secure channel.

Name and contact email:
Report and workspace names (if appropriate to share):
Issue: failed refresh / incorrect figures / access / takeover / AI-generated DAX / other
Who is affected, and which decisions depend on the report?
Business deadline and timezone:
Last known working date and time:
First noticed date and time:
Recent changes:
Exact error text (redacted):

REFRESH
Last successful refresh:
Failed refresh timestamp and error:
Source systems and connection owner (if known):
Gateway involved (if known):
Provider incident or support reference:

INCORRECT FIGURES
Measure and intended business definition:
Expected result and independent source for comparison:
Actual result:
Date range, filters and currency:
A redacted or fictional example:
Was AI used to generate the calculation or model? What was it meant to calculate?

OWNERSHIP AND RECOVERY
Workspace / model / connection owners (roles only, no credentials):
Available PBIX or PBIP files and version history:
Data sources and recovery options known to the administrator:
Changes or fixes already attempted:

ACCEPTANCE
What needs to work after the repair?
Who will check and approve the result?

Preserve the available source files, errors and timestamps before changes.
For exposed data, contact your administrator or security team promptly.

Guide: https://turingbi.com/insights/power-bi-report-broken-what-to-check
Repair: https://turingbi.com/solutions/power-bi-rescue
Enquiry: https://turingbi.com/contact?enquiry=power-bi-rescue#enquiry