Schedule Refresh is failing - Data Source Credentials for the HTTP request response

Hi KR300 

Thank you for reaching out to us on the Microsoft Fabric Community Forum.

We really apologize for the inconvenience, after reviewing the issue of schedule refresh is failing data source credentials for the HTTP request response, here are few steps to may resolve the issue.

• Make sure that all data source credentials are properly configured and authenticated in the Power BI Service.
• Verify that the HTTP request URL is accessible and returns the expected response. If the document hasn’t been published, consider implementing a way to handle 404 errors gracefully in your custom function.
• Adjust the custom function to manage 404 errors without causing the entire refresh to fail. You can return a default value or log the error for further analysis.
• If possible, isolate the HTTP request URL query from the other data sources to identify the issue more easily and prevent it from impacting the overall refresh process.
• The team utilizes additional data sources, including SharePoint Excel and other cloud services, for which the credentials have already been configured in the service. When attempting to enter credentials for the HTTP request URL, they encounter an error because the document has not been published, resulting in a 404 error.

Here is the link to the documentation that might assist in resolving the issue.
https://learn.microsoft.com/en-us/power-bi/connect-data/refresh-scheduled-refresh

If this post was helpful, please give us Kudos and consider marking Accept as solution to assist other members in finding it more easily.

Regards,
Menaka.

Hi KR300 ,

We really apologies for the inconvenience.
Enable "Skip Test Connection" in Power BI Service. Since this HTTP request URL might not always be available, try skipping the test connection when setting up the credentials in Power BI Service:

• Navigate to Power BI Service and go to the Dataset settings.
• Find the HTTP data source.
• Click on Edit credentials.
• Enable the option to Skip test connection.
• Save the changes and try the scheduled refresh again.
  
  If the HTTP check is part of a larger dataset refresh, consider:
• Separating the HTTP request into a standalone table that refreshes independently.
• Using dataflows to manage this step separately from other sources.
  
  If this post was helpful, please give us Kudos and consider marking Accept as solution to assist other members in finding it more easily.
  
  Regards,
  Menaka.