There was a problem saving your refresh schedule. Please try again later.

This should be included in a support request to Microsoft, I do not believe anyone here can help you unfortunately.

Best,

FB

If this helped, please consider giving kudos and mark as a solution

me in replies or I'll lose your thread

Want to check your DAX skills? Answer my biweekly DAX challenges on the kubisco Linkedin page

Consider voting this Power BI idea

Francesco Bergamaschi

MBA, M.Eng, M.Econ, Professor of BI

This is a great question, and it’s something many Power BI users encounter when scheduling refreshes, even with Premium capacity. The error message you shared usually points to a configuration, service, or gateway issue rather than a licensing problem.

1. Verify service and tenant status
   Check Power BI Service Status (https://support.fabric.microsoft.com/en-us/status) to make sure there are no outages or issues in the US Central region (as indicated by your cluster URI).
2. Validate credentials
   
   * Go to Settings → Data source credentials for your dataset.

   * Re-enter or refresh credentials for all sources, even if they appear current — expired tokens or subtle permission changes often trigger this error.

3. Check gateway setup
   

   If you are using an On-premises Data Gateway, make sure:

   * The gateway is online and up-to-date.

   * Data source mappings are correct.

   * No pending gateway updates or expired service accounts.

4. Look for refresh conflicts
   

   Even with Premium:

   * Ensure no other refresh job is running on the same dataset.

   * Avoid overlapping or parallel refresh schedules.

   * Test by temporarily removing one refresh slot and re-adding it.

5. Test the dataset locally
   

   Open the report in Power BI Desktop:

   * Run a manual refresh.

   * Check for schema changes, renamed/deleted columns, or permission issues that could block scheduled refresh.

6. Use your error details
   With your Activity ID and Request ID, open a case with Microsoft Support (https://support.fabric.microsoft.com/). These IDs will help them trace the backend logs for a precise cause.
   
   
7. Quick workaround
   

   If the issue persists:

   * Delete the refresh schedule.

   * Re-publish the dataset.

   * Create a new refresh schedule to reset the configuration.

I hope it will help.