Power BI Report Server October 2020 update has been released.

I have a similar experience which might help Microsoft to identify and resolve the issue.

I upgraded our DEV server to the latest October 2020 version (Version 1.9.7627.11028).

After the upgrade, a scheduled refresh for a Power BI report using a Web connection retrieving data from the ServiceNow API started to fail with the following error:
"Errors":[{"ErrorCode":-1055784932,"Message":"Credentials are required to connect to the Web source. (Source at https://*******.service-now.com/api/now/table/incident.). The exception was raised by the IDbCommand interface.","CallStack":null}

The stored Connection string in PBIRS is the following:
https://*******.service-now.com/api/now/table/incident

I opened the report in Power BI Desktop Version: 2.81.5831.1181 64-bit (May 2020) and saved it. Then I saw that the Connection string in PBIRS got updated to the following:
https://*******.service-now.com/api/now/table/incident?sysparm_query=priority%3D1%5EORpriority%3D2%5Esys_created_on%3E%3Djavascript%3Ags.dateGenerate('2020-01-01'%2C'00%3A00%3A00')&sysparm_display_value=true&sysparm_exclude_reference_link=true&sysparm_fields=number%2Cpriority%2Cincident_state%2Ccategory%2Cshort_description%2Cservice_offering%2Cassignment_group%2Cproblem_id%2Cassigned_to%2Csys_updated_on%2Crfc%2Ccaller_id%2Cclosed_at%2Ccompany%2Csla_due%2Cseverity%2Csys_created_on%2Cstate%2Copened_at%2Curgency%2Ccmdb_ci%2Cresolved_at%2Cu_external_parent_ticket%2Cu_external_problem_ticket%2Cu_external_reference%2Cu_external_ticket

And this made the refresh to start working again. (However, I would say the Connection string should obviously not contain the full API call...)

To confirm that the issue is coming with the new PBIRS version I saved the report to our TEST server, which is still on Version 1.8.7485.35104 (May 2020). Here the Connection string is saved as it was before, that is:
https://ferring.service-now.com/api/now/table/incident

And the refresh also works without any issues on this version.

I really hope Microsoft is able to resolve the issue with the October 2020 version as soon as possible, as the users are screaming for the new features that comes with it.

However, I would never dream of upgrading our PROD server with this release - just imagine having to manually open each report and save it again in order to fix the scheduled refreshes gives my nightmares!

Regards,

Thomas