cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
Resolver I
Resolver I

Flow unexpectedly stopped working out of the blue.....

I don't know what happened, both data sources is accessible.   The flow just stopped out of the blue.

what is going on?

 

I get this error message:

 

Error from token exchange: Connection msmanaged-na/logicflows/d16b7744-3b94-460b-bd3b-b5e8c851badc@https://msmanaged-na.azure-apim.net/ is not allowed to access connection msmanaged-na/sharepointonline/61aa9334874b473b805052b96f55278e

 

 

 

 

9 REPLIES 9
Highlighted
Resolver I
Resolver I

Re: Flow unexpectedly stopped working out of the blue.....

flowerror1.PNG

Highlighted
Community Support
Community Support

Re: Flow unexpectedly stopped working out of the blue.....

Hi @PhilatBaker,

 

What’s your current situation? Are you still having the issue?

From the error code 403, it seems that you don’t have permission to the SharePoint site.

Have you provided proper authorization to access the requested content?

If possible, please try to recreate the connection to SharePoint.

Besides, it’s also possible that the local browser cache could be causing the 403 forbidden error to appear. Please try to clear the cache to see if that fix the issue.

Could you share a full screenshot of your flow? I have made a simple flow to test this issue, however, it cannot be reproduced.

If you are still having the issue, please feel free post back with more details.

 

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.
Highlighted
Resolver I
Resolver I

Re: Flow unexpectedly stopped working out of the blue.....

IRF Notification flow - Error at Personnel Update.PNG

Highlighted
Resolver I
Resolver I

Re: Flow unexpectedly stopped working out of the blue.....

Still doing the same.   I can map this out for you.

 

I have a PowerApp that Patches to 2 SharePoint List:

List 1:  Incident Overview

List 2:  Personnel

 

  1. When a new item is created on the Incident Overview
  2. First Delay it 10 Seconds to finish any delays writing the patch to the lists
  3. "Get" from incident overview list
  4. "Get" from the Personnel List 
  5. Compose Personnel ID formula: last(body('Get_Personnel_Items')?['value'])?['Id']
  6. Update Item the ID of the Personnel list into the Incident Overview list
  7. Update Item of the ID of the Incident Overview List into the Personnel list - where it fails

* kills flow

 

Highlighted
Resolver I
Resolver I

Re: Flow unexpectedly stopped working out of the blue.....

IRF Notification flow - Personnel List Get Details.PNG

Highlighted
Community Support
Community Support

Re: Flow unexpectedly stopped working out of the blue.....

Hi @PhilatBaker,

 

Thanks for updating.

It seems that you are trying to update the ID of each list to each other.

In your last action Update Personal item, please make sure you are using the correct dynamic content ID for the Id field.

I have made the following flow for testing. In my scenario, I am trying to update Id of List A to column ListAId in List B, and update Id of List B to column ListBId in List A.

It is configured likes below.

Action Get items will get items from List B, a Filter query is used to filter out the item has a common value with the new item in list A.

As I am going to update list A using dynamic content from previous action, an apply to each is added automatically, and make sure select the correct dynamic content ID from the action Get item.

Action Update item 2 will update List B, please make sure select the dynamic content ID for the Id field from the action Get items.

Image for your reference.

1.PNG2.PNG3.PNGAAA.PNG

 

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.
Highlighted
Resolver I
Resolver I

Re: Flow unexpectedly stopped working out of the blue.....

I found the problem wasn't Flow. 

 

It was PowerApps.   When it patched some information, it neglected to patch some fields (which still baffles me).  But works ok now.   That information was tied to comparason data that helped the flow.  Once I figured that out, it made sense on why it failed

Highlighted
Community Support
Community Support

Re: Flow unexpectedly stopped working out of the blue.....

Hi @PhilatBaker,

 

Thanks for updating.

It seems that you have figured it out.

 

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.
Highlighted
Frequent Visitor

Re: Flow unexpectedly stopped working out of the blue.....

 


@PhilatBaker wrote:

I found the problem wasn't Flow. 

 

It was PowerApps.   When it patched some information, it neglected to patch some fields (which still baffles me).  But works ok now.   That information was tied to comparason data that helped the flow.  Once I figured that out, it made sense on why it failed



How did powerapps effect a flow that triggers off of sharepoint list? It would trigger just the same if you created the item using the sharepoint list itself.


Helpful resources

Announcements
secondImage

August 2020 CYST Winners!

Check out the winners of the recent 'Can You Solve These?' community challenge!

thirdImage

Experience what's new for Power Automate

Join us for an in-depth look at the new Power Automate features and capabilities at the free Microsoft Business Applications Launch Event.

firstImage

Power Platform 2020 release wave 2 plan

Features releasing from October 2020 through March 2021

thirdimage

Power Automate Community User Group Member Badge

Fill out a quick form to claim your user group badge now!

Users online (3,498)