You’re offline. This is a read only version of the page.
35
Hello guys,
I created a flow responsible for manually sending list items from Sharepoint to AzureDevops. I have a premium license and all connections seem to be correct. The flow works fine for me, but when my users are trying to use it using my connection, they get the following errors:
Flow entity with name xxxxx does not exist in the store!
Do you have any idea what could be the potential cause of this issue?
Good morning,
To move the matter forward. I removed the two inputs when launching the Manually trigger a Flow. I set the variables to functional values. It didn't change anything. I keep searching.
For another need, I made another Sharepoint list with a much simpler Flow... and everything works fine.
It's frustrating.
Best regards
Good morning, I also encounter the same error message - Error e.toLowerCase is not a function.
In my case, I have a SharePoint List and a Flow. The list and Flow are added to a Teams group. The group has three members (owner).
I am the one who “hosts” the Flow and shares it with the Teams group. The three services used in Flow (Sharepoint, Outlook and Teams) are well connected. For me it still works, for my other two colleagues (owner), error. I tried with another colleague who is a member of the group and it doesn't work either.
See attached screen photos for details.
Do not hesitate to suggest possible solutions.
Best regards
I was having this issue come up when trying to use a "Rich text content field" instead of the "Plain text content field" for my Word Template.
Had no issues when switching to use Plain text fields instead (the 2nd option, lighter Aa).
I finally fixed my issue. I was running my flow from the "Run Flow" action of a Business Process Flow stage, and it was not considered "in-context" of the app it was in, so only users with a Power Automate license could run it (it was as if they were running the flow directly from the Power Automate designer studio). After adding the app in the "Associated Apps" section of my flow, the error dissappeared.
I am experiencing this issue when trying to make a new connection on a flow.
Has anyone found a solution? I cannot even build a new connection to reference. Anytime I sign in I get this message.
Hello,
After a few tests i noticed that the issue might come from the reference connection that has been automaticaly generated. Indeed when you add the action to your flow and your flow is in a solution, it automaticaly creates a new connection reference (if you never used this connection before in that particular flow). In my case i thought it might be linked to the name of my solution, because the connection reference is named after it. So i created a new solution and it worked
Regards
Experiencing the same issue. I am using a premium connection (Business Word) and the flow runs for me, however, the run-only users receive this error. Tried adding those users as co-owners and they are receiving the same error. Thoroughly tested my workflow and it was working for run-only users a couple of weeks ago.
I have a premium corporate account and have been having the same issue for about 2 weeks. I suspect that there is some kind of versioning error in the various Microsoft tools, like with the script engine the flow designer IDE. I have similar problems with other MS tools that we know are versioning issues.
#1
WarrenBelz
146,587
Most Valuable Professional
#2
RandyHayes
76,287
Super User 2024 Season 1
#3
Pstork1
65,928
Most Valuable Professional
Share
Report
All responses (
Answers (
