Windows 7 Crazy Error Maker
Helen Drewski
I get that sometimes lately switching between shops especially if I try to partially erase the prefilled info and edit it with shops that have similar names or use saved info. Better to fill it all in from scratch. It usually only errors on me the first time though. If you're using saved shop names/passwords try filling them all in from scratch.
This has been and still is happening to me for the last several weeks. Usually even though it says error you cannot sign in, you are actually signed in. Just click on the Etsy logo at the top left of the page and you will see that you are signed in.
I am keeping your solution, ChristmasIsLove and yours, BikerBlingCa in my back pocket in case I need to try something different in the future (should this happen again) as I bet those will both work as well !!!
:: Having this too, for the last few weeks, EVERY time I sign in, get the error msg... don't pre-fill info etc and private browsing etc never used to happen... so some new reason why it's happening now for people... easy way around is just remove last digit of password, then add again... but still, should not be happening! ::
When I get this stupid Error Banner, I do Ctrl F5 (a hard Refresh), and I am in. But the point is, I don't know WHY I have been getting the Error Banner (always use the same desktop computer, Chrome, Windows 10 for everything). It doesn't make sense, to have to do a workaround like this.
Oh yes it is a DAILY thing..about 50/50 . I sign in and out between shops numerous times a day. It has gotten to the point I hardly even notice it, jus tdeal with it but when you thinkabout it it is an ETSY issue as I am not getting sign in errors anywhere else and it has been happening all year.
I was having the Captcha screen (verify you are a human) a while back maybe last year and I think I needed to update my browser to fix it - you might check to see if yours is up-to-date. As far as the error/refresh situation, I have learned to live with it but at least I can get in (for now anyway)....best of luck!
Yes I know what to do when this happens. How many Shoppers Know how to log on to Etsy? is this what is happening to shoppers, their shopping Else where due to Frustration Not being able to log onto Etsy? *Refresh the page to log onto Etsy.
Not sure if I can reply here as I have closed my Etsy shops since posting on this thread. As a buyer (or trying to be a buyer) on this site, I still get this crazy error message every time I try to sign in. Because I used to sell here, I know that all I have to do is refresh or click the Etsy logo as I am actually signed in even though it says I am not. Also, getting the captcha lately.
It's so strange. My issue, which was the exact same error, was definitely caused by the connection references, I'm sure.
Are you importing separate solutions? I.e Flows and Connection References first, and then another solution with the app?
The first solution I imported contained my Flow, Customer Connector and Connection Reference.
Then another solution with my SQL Flow and SQL Connection Reference.
And finally a solution with my Apps.
I did not import separate solutions when you had mentioned it may be a corrupted solution, instead I just deleted the entire solution from the target environment and reimported the entire solution. So your solution may still work.
However, I am hesitant to delete the solution again and import the separate solutions, as the last time I did this, it caused another issue with the security roles and I was not able to access the system for the rest of the day.
4. In the target environment (Prod environment for me), check if there are any unmanaged layers on the app or flow and delete them. This is done by selecting the three vertical dots next to the flow or app, selecting Advanced, then See solution layers. If a solution is unmanaged it will indicate so under the Solution column. Select the unmanaged layer and remove it.
@BradonK Currently I'm struggeling with the same error "Failed to install flow" for a specific power app and it's related power automate power apps v2 triggered flow in a PROD environment managed in a solution. I came across your post Solved: Failed to install flow error - Power Platform Community (microsoft.com) as I was going crazy about this error in the last days. Thanks for your post!
Seems like somehow the connection breaks between power apps and power automate which leads to the error message "Failed to install the flow" for you. Reconnection seems to fix your issue in the magical way microsoft support has explained.
For my part it is/was something different that leads too the error: "Failed to install the flow" but I think the solutions are somehow related. As I'm struggeling with solution layers in context of this error.
Our current situation:
We got DEV environments and PROD environments, after development we are exporting/importing our solutions mostly containing multiple flows and a app from DEV to PROD environment. Most of the solutions work in the context of the users connections. Using a workaround for sharepoint permissions to let the users create items in sharepoint lists but not allowing them to see these lists. (Workaround as mentioned here by @WarrenBelz Solved: Sharing a Power App without Sharing the Sharepoint... - Power Platform Community (microsoft....)
Recently we started to work with "Run only users" feature of power automate to run power apps v2 triggered flow with elevated permissions with a IT department controlled service account. To avoid using the Sharepoint permission workaround mentioned above.
The error "Failed to install the flow" start appearing to us after we setup the flows in the PROD environment with the "Run only users" feature to use the IT departments controlled service account. Users suddenly were confronted with this error after changing to this setting. After removing the configuration by deleting the unmanaged layer the flow worked fine again in the context of the users / using their own connection. In our situation it look like the error is caused by the unmanaged layer that is created when setting up the "Run only users" configuration in the PROD environment. Deleting the unmanaged layer seems to solve the problem but it does not help us to reach our goal of use the IT departments controlled service account with elevated permissions.
But here is the point that makes me crazy:
I really do not like unmanaged layers on top of my flows in the productive environment. As they lead to confusion during app / solution updates. I would like to setup the "Run only users" configuration in the DEV environment and move it to the PROD without the need of an unmanaged layer.
But as far as I understand the concept of "Run only user" configuration in the targeted environment you always created unmanaged layers in PROD environments. If you configure the "Run only users" settings as you have to choose these connections after import of the solution.
Or do I get something wrong here? Is it possible to setup the "Run only users" already in DEV and move it of PROD using the Service Account connection already in DEV?
Thanks for any help.
I can answer my question now by myself. I've implemented it as described for three soltuions today, all of them are working as expected. I also testetd it with our endusers.
Answer to my question:
Yes you can setup the "Run only user" for a PowerApps V2 triggered flows in DEV with a Service Account connection, then move the solution to the PROD environment without the need of creating an unamanaged layer.
How?
1. Create service account connection in your dev environment (beeing logged in with your personal account where the solutions lies) for each connector you use in the flow that uses the "Power Apps V2 trigger".
2. Create - if not already there a serivce account connection for each connector required in PROD environment beeing logged in as the service acccount
6. Import your solution using your Service account
This worked for me for three solutions and there corresponding apps. This way also makes the special sharepoint permission needless as described in my last post. You just have to permit the service account for the specific resource.
Any other tips or comments are highly appreciated.
Cheers!
Repeatedly tried to export from Dev as a Managed Solution and import into Prod but whenever users tried to call the Flows from the App, they got messages about missing privileges or about the Flows not being installed. Everything ran fine for the service account used to do the actual import.
I just did a 'traditional' Power App export/import to move the App/Flows to the Prod environment and everything works as it should* - no changes to user roles/permissions, so this suggests to me that there are bugs in the Managed Solution deployment system.
*The environment variables are already in place from the earlier attempt to import the solution - the only issue I found is that one of the flows had a reference to an environment variable and when run, it was using the variable value from Dev instead of Prod. I removed the reference from the Flow and added back in the exact same reference and saved... hey presto, it now uses the expected (Prod) value. References to other environment variables also used the expected values.
Dear Community Members, We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd. During this period, members will not be able to Kudo, Comment, or Reply to any posts. On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities. What to Expect in the New Community:A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates.We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!
ff7609af8f