For A Selected Item trigger: Something went wrong

(0) Share

Report

Posted on by rose01162020

Good Day!

I have a query.

This is the issue/scenario.

We are using a "For a selected item" (in sharepoint) instant flow trigger. It's being triggered via automate button in SharePoint list see below image

It is working just fine until just today, the user raised a concern that a message is showing saying that "Something went wrong" see image below for reference.

Error Running Flow.png

Process:

1. user selected an item.

2.clicked automate> selected the flow> clicked run Flow button

3. Upon clicking the run flow button, the error message popped up.

The user already did the following:

1.restart the PC

2.used another browser

3.updated the browser to the latest version

...but same issue is being encountered.

It is working just fine when I and my other colleague triggered the same flow,

We would like to know if you encounter the same issue and what steps did you make to resolve this?

thank you

Categories:

General topics

I have the same question (0)

All responses (6)

Answers (0)

rose01162020 10 on at

Like (0)

Report
Copy link

Link copied!

update: User tried to use another PC but same scenario was encountered. any solutions regarding this? is this an account issue since device was eliminated ?

Was this reply helpful? Yes No
RamMaddela on at

Like (0)

Report
Copy link

Link copied!

Did you find the solution for this problem? I'm encountering the same issue

Was this reply helpful? Yes No
rose01162020 10 on at

Like (0)

Report
Copy link

Link copied!

Hi, based on our coordination with MS Support.

Here is the root cause. Please see below link:
https://docs.microsoft.com/en-US/troubleshoot/power-platform/power-automate/client-request-aborted-failed-fetch

Here is the Solution Provided:
Please help contact your administrator or IT department to unblock access and allow below IPs and domains.

- Please use the following IP addresses in your allow list to facilitate Power Platform requests.
https://docs.microsoft.com/en-us/connectors/common/outbound-ip-addresses#power-platform

- Please ensure none of these services are blocked on your network.
https://docs.microsoft.com/en-us/power-automate/ip-address-configuration#required-services

- Please also allow below IP if you need to use HTTP or HTTP + Open API.
https://docs.microsoft.com/en-us/azure/logic-apps/logic-apps-limits-and-config?tabs=azure-portal#firewall-configuration-ip-addresses-and-service-tags

Hope this helps.

Thank you

Was this reply helpful? Yes No
RamMaddela on at

Like (0)

Report
Copy link

Link copied!

Thank you so much rose. I appreciate it.
Cheers

Was this reply helpful? Yes No
NaufalP 75 on at

Like (0)

Report
Copy link

Link copied!

Hi there,
Is there another root cause of this aside from the blocked IP from the IT?

We had this issue with one of our user today when before he was running the flow fine. Our workaround was asking the user to trigger the flow using Incognito Mode and it works normally.

Was this reply helpful? Yes No
RamMaddela on at

Like (0)

Report
Copy link

Link copied!

One of the solution for this problem is removing the trigger and adding it back again to the flow.

Was this reply helpful? Yes No