Power BI Refresh Schedule and Gateway Planning Notes
Plan data refresh, ownership and failure handling.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Plan data refresh for a Power BI report. Data sources and where they live (cloud, on-premises files, databases): [SOURCES]. How often the source data changes: [CHANGE_FREQUENCY]. When people need fresh numbers: [FRESHNESS_NEEDS]. Dataset size and refresh time: [SIZE_AND_TIME]. Who owns the report: [OWNER]. Present a table with Source, Frequency, Time, Owner and Failure action. Recommend a schedule with times, say whether a gateway is needed for on-premises sources [VERIFY with IT], who maintains credentials, and what limits my licence may impose on the number of refreshes [VERIFY]. Describe incremental refresh for large tables and when it is worth the effort. Failure plan: who is alerted, the first three checks (credentials, source availability, data changes), and how to tell users data is delayed. Add a freshness label on the report page showing the last refreshed date and time, and a monthly check of refresh history. Do not ask me for passwords or connection strings; use placeholders. List the questions to ask IT before scheduling.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.