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.
"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: '."
Solved! Go to Solution.
I found the answer to this issue in the comments of the original announcement: http://disq.us/p/25hsod0
"That means that this feature is not yet available for your environment. You can try this out by creating a new environment, or, wait until the feature is rolled out everywhere, which will be a few weeks."
Also in the original announcement (Nov 6th): "The public preview of attended automation will be enabled for all new environments by the end of the week and enabled for all existing environments before the end of November."
Hope that helps! I created a 30 day environment to validate and all is working well with that.
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.
- create an instant flow and a UI flow from an action within that
- successfully test my UI flow (types text in notepad)
- when testing from an instant flow, UI flow action fails with the message above.
I've talked with another person (besides @edim's report above) that is experiencing this. Can you help us move past it?
@v-litu-msft , Thanks for the response.
I can't seem to get past the flowsessions error.
The UI Web Flow works in Selenium with no errors. When added to the UI flow web card, card is able to recognize the parameters. But on testing the API failed error continues to occur.
Is there a glitch in the system?
I am also experiencing this. Does it have to do with the environment or organization policies that I am in?
using web ui. flow works like a charm from selenium, but when try to execute/test flow - then this 'flowsessions' error 😞
@v-litu-msft , is there an update on this issue. It appears not to be a localized or individual issue only. My company wants to move over to MS for RPA instead of our current RPA tool, but we can't if this issue is not resolvable.
Thank you for the help.
Features releasing from October 2020 through March 2021
We are excited to announce the launch of Power Virtual Agents Community. Check it out now!
We've updated and improved the layout and uploading format of the Power Automate Cookbook!
Fill out a quick form to claim your user group badge now!