Desktop UI Flow - Request to XRM API failed with error: 'Message: Resource not found for the segment 'flowsessions'

[topness]

Hi Power Automate team,

I'm trying out Desktop UI Flows, using a simple flow that takes a parameter, opens notepad and types it in, then saves the file with a random filename.  I'm able to get the UI Flow to work fine in test mode.  When I try to invoke it from an Instant Flow, it fails with the error shown below (full error message below it).  I have a 2 minute video of the process here:  https://youtu.be/Fl3PMKEDEJU

Is this post-release preview jitters or something I'm doing wrong?

I'm using a default environment in region North America.

{
"error": {
"code": "XrmApiRequestFailed",
"message": "Request to XRM API failed with error: 'Message: Resource not found for the segment 'flowsessions'.\nCode: 0x8006088a\nInnerError: Type: Microsoft.OData.UriParser.ODataUnrecognizedPathException\nMessage: Resource not found for the segment 'flowsessions'.\nStackTrace: at Microsoft.OData.UriParser.ODataPathParser.CreateDynamicPathSegment(ODataPathSegment previous, String identifier, String parenthesisExpression)\r\n at Microsoft.OData.UriParser.ODataPathParser.CreateFirstSegment(String segmentText)\r\n at Microsoft.OData.UriParser.ODataPathParser.ParsePath(ICollection`1 segments)\r\n at Microsoft.OData.UriParser.ODataPathFactory.BindPath(ICollection`1 segments, ODataUriParserConfiguration configuration)\r\n at Microsoft.OData.UriParser.ODataUriParser.Initialize()\r\n at System.Web.OData.Routing.DefaultODataPathHandler.Parse(String serviceRoot, String odataPath, IServiceProvider requestContainer, Boolean template)\r\n at System.Web.OData.Routing.DefaultODataPathHandler.Parse(String serviceRoot, String odataPath, IServiceProvider requestContainer)\r\n at Microsoft.Crm.Extensibility.ODataV4.Routing.CrmODataPathHandler.Parse(String serviceRoot, String odataPath, IServiceProvider requestContainer)\nInternalException: '."
}
}

[Anonymous]

I wish it was a more clear message on whether we have access to or not.

So I thought all the work I did to record the steps was lost, but I can click click around to "Edit" or "Test" somewhat.

[arun_ap]

I also get the same error when using UI Flow for Web. Is there any workaround available?

[maCs]

I also get the same error when using UI Flow for Web

[colonel_claypoo]

Same error here, still. Hope it'll have rolled out soon.

[KristianB]

Just to support this blog entry. I'm experiencing the same issue. Configured everything like the doc mentioned (Gateway, Connection, etc.) but still getting the error. Testing UI Flow works like a charm but can not trigger it through a Flow. Tested it in two tenants (work & personal environment) and different environments (default and a new created one) and everywhere the same error.

[KristianB · Accepted solution]

I got an answer from a software engineer from Microsoft. You need to create a new environment to avoid this error. This happens only in existing environments and Microsoft is working to backfill existing environments.

[topness]

Thanks @KristianB I was able to create a new environment and successfully automate a desktop UI Flow from Power Automate.

[pmendez]

Me parece que ese error es por un tema de regiónes, el Gateway y la suscrpción de O365 deben estar en la misma región. Hice la siguiente prueba:

Cree una nueva suscripción de O365 (Trial) con región de "USA"

Instale On-Premises data gateway

Configure On-Premises data gateway

Ingrese a Power Automate

Cree un nuevo entorno con región de "USA"

Cree un flujo de interfaz de usuario

Luego guarde mi UIFlow

Cree un flujo de automatización desde cero

Desde el flujo de automatización dispare mi UIFlow y todo OK.

[pmendez]

La región del tenant de Office 365 y la región del gateway deben ser iguales

[rmcleod45]

I am getting the same error, 

Request to XRM API failed with error: 'Message: Resource not found for the segment 'flowsessions'.\nCode: 0x8006088a\nInnerError: Type: Microsoft.OData.UriParser.ODataUnrecognizedPathException\nMessage: Resource not found for the segment 'flowsessions'

... etc.

Is this the issue that was mentioned about. Old environments still won't have this feature?

In the release it said that all environments would be enabled by the end of November?