cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
ericonline
Community Champion
Community Champion

ERROR: Save Conflict help

I have a critical flow that just failed. I need some help determining WHY this failure occurred and how to prevent it in the future. 

Flow:

Trigger: PowerApps

Action1: Parse JSON

Logic1: Apply to each

  - Action2: Create File (Sharepoint Doc Library)

    - This is where the error occurred:

 

Save Conflict

Your changes conflict with those made concurrently by another user. If you want your changes to be applied, click Back in your Web browser, refresh the page, and resubmit your changes.
clientRequestId: 2d9401b7-1149-45f4-8bc1-77485e52c47c
serviceRequestId: 2d9401b7-1149-45f4-8bc1-77485e52c47c

 

  - Action3: Update File Properties (Sharepoint Doc Library)

    - Adds metatdata (columns) to file just created

Flow has been running fine for months.

Oddly enough, there were two files being created; error only occurred on the first. Second file was successful. 

ericonline_1-1596145596392.png

ericonline_2-1596145609080.png

Thoughts on how to troubleshoot this? 

 

1 ACCEPTED SOLUTION

Accepted Solutions

Hello @ericonline 

What you can do is to insert a parallel branch after the Create image file, so that you have one branch that update file properties when the Create action succeeds, and another branch to handle the situation when it fails.

The failure branch could then first inform you (Send email), then a delay, before retrying to create the image file and update the properties.

You could put the above into a Do until loop, that will retry X number of times or for Y minutes - you will have to track the success/failure so you can exit the loop when success is the result. You will also have to handle the event if the Do until loop expires (X loops, or Y minutes) - again with a parallel branching after the loop.

Just be careful with parallel branches, when merging them back into one, the Configure run after options must be set correctly 🙂

Hope the above helps a little. Kind regards, John

View solution in original post

14 REPLIES 14
JohnAageAnderse
Memorable Member
Memorable Member

Hello @ericonline 

Could you describe more about how the files in your flow run were created?

Do you have any other flow running on the same library/list that may have modified the file?

Anything else you could tell us about?

Kind regards, John

Hi @JohnAageAnderse ,

There really isn't much to the file creation:

- Get some attributes and base64 image(s) from PowerApps

- Parse values and base64 out

- Create file(s) from the .jpg base64

- Update properties (columns) associated with file (.jpg)

image.png

- Again, the second file in this case is successful

 

 

- There is another Flow that runs against this Document Library. 

  - How does Sharepoint handle concurrent requests to Documents?

 

Hello @ericonline 

As you are only creating the files in the flow, there should be no concurrent issues.

Could you provide screenshots of how the flow looks like, not the run, but the actions, expanded.

The first image file that is created and fails, does it have a name that already exists in the library? or are the names unique upon creation?

Are there any difference between the two files, meaning the parameters provided from PowerApps?

Could you take the parameters for the first file and manually create the file? For example by using a simple manual flow to hold the values in variables and then create the file from those?

Kind regards, John

1. image.png

2. Filenames are unique. Created in PowerApps with a milliseconds timestamp

3. Differences between two files: Filename, File Content and imageNotes

4. No issue creating the file manually...

  - image.png

Hello @ericonline 

Thank you for the information 🙂

I didn't see that you updated the file properties after the creation. Could you add a delay action between the creation and the update, just to confirm that the update is not taking place while the file is being created. Try with 30 seconds at first.

Kind regards, John

Yeah, the Flow has been running without issue up until this fail, so adding a timer won't positively affirm it as a fix. I need to know WHY this error occurs (the conditions that trigger the error message) so I can mitigate. 

This is a critical Flow, so one fail like this hurts the integrity of my solution as well as the image of Flow as a business critical tool. I want to architect the solution to mitigate against errors like this. But to do so, I need to know what causes the error.

image.png

Hello @ericonline 

What you can do is to insert a parallel branch after the Create image file, so that you have one branch that update file properties when the Create action succeeds, and another branch to handle the situation when it fails.

The failure branch could then first inform you (Send email), then a delay, before retrying to create the image file and update the properties.

You could put the above into a Do until loop, that will retry X number of times or for Y minutes - you will have to track the success/failure so you can exit the loop when success is the result. You will also have to handle the event if the Do until loop expires (X loops, or Y minutes) - again with a parallel branching after the loop.

Just be careful with parallel branches, when merging them back into one, the Configure run after options must be set correctly 🙂

Hope the above helps a little. Kind regards, John

Thank you for the continued engagement @JohnAageAnderse . I'm very interested in your "do until" approach. I've used "Configure run after" in a similar manner, but have never seen the pattern that will retry a Flow if it fails. 

I know its a big ask of your time, but would you mind showing a screenshot of the "do until" actions?

I'd really appreciate it. 

Hello @ericonline 

I can show you one Do until example that we have in production - it is about getting a reason for why a change was made and we uses the Approvals to ask for that.

 

It starts with initialization of variables - one of which is used to track whether or not we had a successful outcome in the Do until loop - that is the variable "ResponseReceived" (boolean, value false).

The Do until loop will continue to loop till either:

  • the variable "ResponseReceived" is true
  • the loop has looped 4 times (see the Count field)
  • or the loop has been running for 9 hours (see the Timeout field)

An approval is requested and we have configured the Wait for approval to only wait 2 hours, after which it fails.

Do until response received or expiredDo until response received or expired

The Condition after the Wait for approval only runs if the Wait for approval succeeded, and it just checks to see if we got a response. If not, we loop one more time! If we got the response, we set the variable "ResponseReceived" to true and the Do until loop then exits.

Now if the Wait for approval expires after 2 hours, then the Condition is not executed, but the following action "ResponseComment eq Please provide a reason for the change" is executed, and we loop again, trying again to get a reason 🙂

If no success, try againIf no success, try again

Hope the above gives you the idea on how to use the Do until loop to check for success, failure, or simply giving up 🙂 We do have an action after the Do until loop that checks for the loop result, so if the loop failed (expired), then the system owner is informed and will contact the "bad" guy 😄

Kind regards, John

Hello @ericonline ,

 

I got the same error sometimes while creating file when 'new email arrives' event.

 

Could you please let me know how you used 'Do Until' method in your case? What did you checked in that?(screen shot will be good help).

Also, a 'Cannot open file' is too there for 1 time in same 'create file' action.

 

panand99_0-1611169136317.png

 

ericonline
Community Champion
Community Champion

This problem "just went away". I didn't change the Flow at all, just waited. 

Hello @ericonline ,

 

That is Great.

But can you please help on this case how/what to check as I need to add in this condition here.

 

Thanks in advance.

 

Hello @panand99 

Do you have another flow for that document library that reacts when you create a file?

Kind regards, John

Hello @JohnAageAnderse 

 

This problem has been solved, I used a variable and sets it on the case when records is created.

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 | Winners will be 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

Users online (2,892)