cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Colin_Davis
Frequent Visitor

Flow works for the creator but not after its shared

I have built a flow that works perfectly fine for me. But as soon as I share it with my team they are getting a 404 error.

It happens on the first action when the flow tries to connect to their Outlook account.

 

Screen Shot 2018-10-12 at 1.41.04 PM.png

 

Any ideas? Am I sharing it wrong? I have tried exporting as .zip, and sharing by adding owners. Thanks in advance

 

1 ACCEPTED SOLUTION

Accepted Solutions

Hello Mabel,

So after some troubleshooting I figured out the problem, and it seems that it's actually in the source code of Flow itself. I'll try to explain it the best as possible...

 

The first action is "When and email it flagged", the default folder for this action to monitor on is the users Inbox, I'll call this the "Defualt Folder" for the rest of this post.

 

If I NEVER CHANGE that Deafult INBOX folder in that first action and then build the flow as needed everything works as expected. I can then share the flow whether by exporting a .zip package or adding a co-worker as an owner, or making it a team flow, and have no issues. 

 

Now if I change the Default INBOX folder in the first action (When an Email is Flagged) from INBOX to anything else (Sent Items, Drafts, etc.) it will run perfectly fine on my account (I am the creator of the flow) but if I share it, in anyway, with anyone, the very first action will get the error above. Even if I change the Default INBOX Folder to something else and BACK TO Inbox it gets an error when it is shared. But again I can change it to anything on and it runs fine on my account, but only my account. Its almost like whatever the code is changed in the flow when switching that folder writes itself in such a way that when shared it breaks. (I have not had time to delve into what that code is as of yet)

 

Here's where it gets really weird. Once I share the working flow (with the Default INBOX Folder NEVER changed) and another user makes a copy on their account then changes the folder themselves, it works fine. 

 

TL;DR: you cant change the first action folder and share the finished flow. It breaks. 

View solution in original post

4 REPLIES 4
v-yamao-msft
Community Support
Community Support

Hi @Colin_Davis,

 

How did you share the flow? Have you shared the flow as Owners?

Can your co-workers check the shared flow under Teams flows?

You mentioned that you have tried exporting the flow, have your co-workers imported with their own connections?

Here is a blog about how to share with office 365 groups, please check it at here:

https://flow.microsoft.com/en-us/blog/share-with-sharepoint-office-365/

 

Best regards,

Mabel

Community Support Team _ Mabel Mao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Hello Mabel,

So after some troubleshooting I figured out the problem, and it seems that it's actually in the source code of Flow itself. I'll try to explain it the best as possible...

 

The first action is "When and email it flagged", the default folder for this action to monitor on is the users Inbox, I'll call this the "Defualt Folder" for the rest of this post.

 

If I NEVER CHANGE that Deafult INBOX folder in that first action and then build the flow as needed everything works as expected. I can then share the flow whether by exporting a .zip package or adding a co-worker as an owner, or making it a team flow, and have no issues. 

 

Now if I change the Default INBOX folder in the first action (When an Email is Flagged) from INBOX to anything else (Sent Items, Drafts, etc.) it will run perfectly fine on my account (I am the creator of the flow) but if I share it, in anyway, with anyone, the very first action will get the error above. Even if I change the Default INBOX Folder to something else and BACK TO Inbox it gets an error when it is shared. But again I can change it to anything on and it runs fine on my account, but only my account. Its almost like whatever the code is changed in the flow when switching that folder writes itself in such a way that when shared it breaks. (I have not had time to delve into what that code is as of yet)

 

Here's where it gets really weird. Once I share the working flow (with the Default INBOX Folder NEVER changed) and another user makes a copy on their account then changes the folder themselves, it works fine. 

 

TL;DR: you cant change the first action folder and share the finished flow. It breaks. 

Hi @Colin_Davis,

 

Thanks for sharing the detailed info.

I am glad to hear that you have figured out the issue.

 

Best regards,

Mabel

Community Support Team _ Mabel Mao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
GabrielStJohn
Community Champion
Community Champion

Hey, @Colin_Davis!

Thank you for posting to the Flow Community Forum! It appears you have found a solution to your issue! If you feel as though your issue has been solved and you are satisfied with one of the previous replies, please click "Accept as Solution" on the reply that contains the solution so that this thread will be marked for other users to easily identify!

Thank you for being an active member of the Flow Community!

-Gabriel
Microsoft Flow Community Manager

- Gabriel
Community Manager
Power Automate | Power Virtual Agents
Super User Program Manager



Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

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!

Summer of Solutions | Week 4 Results | Results posted on July 24th

We are excited to announce the Summer of Solutions Challenge!    This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Community MembersNumber SolutionsSuper UsersNumber Solutions Deenuji 9 @NathanAlvares24  17 @Anil_g  7 @ManishSolanki  13 @eetuRobo  5 @David_MA  10 @VishnuReddy1997  5 @SpongYe  9JhonatanOB19932 (tie) @Nived_Nambiar  8 @maltie  2 (tie)   @PA-Noob  2 (tie)   @LukeMcG  2 (tie)   @tgut03  2 (tie)       Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 2: Community MembersSolutionsSuper UsersSolutionsPower Automate  @Deenuji  12@ManishSolanki 19 @Anil_g  10 @NathanAlvares24  17 @VishnuReddy1997  6 @Expiscornovus  10 @Tjan  5 @Nived_Nambiar  10 @eetuRobo  3 @SudeepGhatakNZ 8     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji32ManishSolanki55VishnuReddy199724NathanAlvares2444Anil_g22SudeepGhatakNZ40eetuRobo18Nived_Nambiar28Tjan8David_MA22   Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 4:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji11FLMike31Sayan11ManishSolanki16VishnuReddy199710creativeopinion14Akshansh-Sharma3SudeepGhatakNZ7claudiovc2CFernandes5 misc2Nived_Nambiar5 Usernametwice232rzaneti5 eetuRobo2   Anil_g2   SharonS2  

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Top Kudoed Authors
Users online (3,363)