Unexpected error. Unable to fetch

[Haithamalsheikh]

Hi,

I’m a new on Power Automate and I created a flow to calculate how many days overdue date payment so the idea I have a lot of orders and I have to receive an email if one of these orders exceeds 70 days overdue date from tables (JAN,FEB,March..etc)

In the beginning, the flow was working perfectly and it was only one table, I added more tables for each month as branch parallel as below and when I do a test sometimes I get an error that says Unable to fetch sometimes that error came on excel table action and sometime to another action such filter array or compose. This error is disappointing me ☹.

I created another flow without a branch parallel but the issue still repeated!

Please check my flow below and advise if there are any issue from my side:

1. Initialize variable.
2. Step excel (business) from onedrive.
3. filter array (filtering pending orders to reduce result of that table
4. Compose for filter array on previous step.
5. another filter array from output previous compose to filtering the overdue days.

@less(item()?['BAYAN DATE'], addDays(utcNow(), -70))

1. Compose for filter array on previous step.
2. for each the output from previous Compose step.
3. inside for each append array to extract the data from for each.

Outside of branch parallel:

1. Compose for Initialize variable.
2. Create HTML Table from previous Compose step.
3. Send email.

I need your support to solve my issue please.

[SimonLavisUOS]

I have the same issue constantly. It seems the 'Unable to fetch' is related to recalling information about the flow run, but it makes troubleshooting impossible much of the time, and I can get zero support. The community questions on this topic go unanswered, the documentation doesn't refer to this issue, and no one at Microsoft seem to want to address people when we raise this.

[StanDiamond]

I'm having the same problem.  Surely there must be a fix for this.

[SimonLavisUOS]

Hi @StanDiamond. We eventually had our IT team send a support ticket and after a lot of runaround, Microsoft essentially pointed to the problem being that free PA accounts have extremely limited fetch limits which seem to be triggered/maxed out by simply opening the flow itself and calling information about the actions, so by the time you get to expanding an action you're fetch-limited. As far as they're concerned, this is not an issue because it's down to the user, not the system, and is resolvable by paying for a more enhanced license. 

In our case we needed to upgrade to a better licence for other reasons, but this was super disappointing and not in any way made clear. Not sure if this is intended to promote upgrades, but they don't see the problem for end users at all in this respect.

[StanDiamond]

Hi @SimonLavisUOS , thanks for that very helpful explanation.  I guess I will just have to live with the problem.  I do find that the occurrence of the Unable To Fetch error is quite random.  Looking at the individual passes in a Apply To Each action gives the error on some and not on others, and of course the one I'm interested can be one that errors. However with persistence, going backwards and forwards with Next> and <Previous  I can eventually see it. All a bit tedious.  Thanks again.