Excel Automate: New Script → Error Message

[Anonymous]

In Excel I can't create new or access already existing scripts in the Automate ribbon. After a moment the following error message appears:

// German

"Ein unerwarteter Fehler ist aufgetreten. Schließen Sie den Aufgaben Bereich, um es erneut zu versuchen.
Wir konnten Ihre Skripts nicht laden. Versuchen Sie es erneut."

// English

"An unexpected error occurred. Close the task pane to try again.
We could not load your scripts. Try it again."

How can this problem be solved?

Thank you in advance and best regards,

Daniel

[Yutao]

@Anonymous - sorry to hear you were experiencing issue when creating script. Is it still happening now?

[Anonymous · Accepted solution]

@Yutao No, two days later it suddenly worked without me having done anything. Since then the issue never reoccured.

[Anonymous]

can help to share how to solve this issue

[Yutao]

@Anonymous -

We are aware of intermittent authorization failures that might be causing this. We have been actively looking into it and will update back with more details. Thanks for your patience!

[delphi]

same issue. Please update status A.S.A.P 

[Yutao · Accepted solution]

Update: we are still working with our partner teams to track down the issues and possible solutions. Based on the information we have collected so far, we suspect the issue might be related to this admin settings: SharePoint and OneDrive unmanaged device access controls for administrators - SharePoint in Microsof...

If possible, can you folks help to reach out to your SharePoint admins or tenant admins and check if the particular policy (block access from unmanaged devices) mentioned in the above article is turned on or off, or if they are aware of this policy at all?

Thanks again for your patience and support!

[delphi]

If we turn off block access from unmanaged devices

it looks like solve the issue, however this action will break organization information security policy

which bypass access control, which is unacceptable

[Anonymous]

FYI - although not a good solution, it is A solution. This is why I'll mark it as such.

[Yutao]

Hi all, please follow this thread for any further updates: Execute Excel Script - Unauthorized - Power Platform Community (microsoft.com). Thank you!

[ryan666]

Any updates? I just noticed this for the first time today.

Not sure I can afford to just wait/hope that this goes away.

And

And I believe that whatever is going on might be the cause of this Power Automate issue as well:

[ryan666]

The full Power Automate 'Run Script' error that Im getting:

Could not retrieve values. The dynamic invocation request failed with error: Unexpected error occurred when calling the ApiHubsRuntime API: 'Microsoft.Azure.ProcessSimple.Data.Entities.Exceptions.ProcessSimpleDataException: The ApiHubsRuntime API call failed with http status code 'BadGateway' and response content '{ "error": { "code": 502, "source": "canada-001.azure-apim.net", "clientRequestId": "a0b46dab-1799-4988-8fa3-b63ab5b88c98", "message": "BadGateway", "innerError": { "status": 502, "message": "The server experienced an issue and couldn't complete the request. Please try again in a few moments.\r\nclientRequestId: a0b46dab-1799-4988-8fa3-b63ab5b88c98", "error": { "message": "The server experienced an issue and couldn't complete the request. Please try again in a few moments." }, "source": "excelonline-ce.azconn-ce-001.p.azurewebsites.net" } } }' at Microsoft.Azure.ProcessSimple.Data.DataProviders.HttpClientDataProvider.<>c__DisplayClass47_1`2.<<CallService>b__0>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.WindowsAzure.ResourceStack.Common.Algorithms.AsyncRetry.<Retry>d__3`1.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1.ConfiguredTaskAwaiter.GetResult() at Microsoft.Azure.ProcessSimple.Data.DataProviders.HttpClientDataProvider.<CallService>d__47`2.MoveNext()'.

[Yutao]

@ryan666 -

Sorry to hear you were experiencing the issue with the Run script action. We were aware of an outage in one of the services we depend on that might have potentially caused the problem. A patch is being rolled out at the moment. Please give it a try and let me know if the issue persists. Thanks for your patience and support!

[ryan666]

Thanks for the reply. the problem seems to still be happening.

I continue to try and will update.

[Yutao]

@ryan666 - can you share the clientRequestId of the failed Run scrip action? You can find that ID from the Error Details pane on the run history page.

[ryan666]

Hi and yes. Here it is:

clientRequestId: 1ebcd360-b66d-4659-942e-997359602f80

 Edit: Actually that is just one I was toying with to try to get around the problem.

Here is what the desired one is like:

clientRequestId: 4a350312-b907-4a24-b137-e7bf5a94380b

The steps look like this:

The 'Outputs' in ScriptParameters is my image.

The script itself is in a compose and dropped into the Script field as custom value because I cant search for actual scripts due to the error:

[ryan666]

All is back to normal again. Thanks to Yutao for your interest in helping.

I have 2 workstations: One in Canada and another in Poland.

The Canadian one started working yesterday. The Poland one now works today.

My o365 tenant is in Canada.

Not sure if any of that info is helpful ..... but like the others who reported this, I just had to wait.

[Yutao]

Thank you for sharing the info @ryan666 ! Yea unfortunately it seems the patch rollout took a bit longer than expected. But I believe it is fully rolled out now.

As always, thanks again for everyone's patience and support!