Unanswered

Excel dynamic content failing in condition within loop

(0) Share

Report

Posted on by michowl Microsoft Employee

I've got an odd Action Failed error in a loop. I can't look at what the values of the condition are. Nor can I scroll through the results of each iteration like I usually can with a successful flow.

First image is what I"m trying to do, the second is the error I get when I run values through. Note, with this case, I have verified that the User Profile Department contains the string of one row Department in the Excel sheet.

Categories:

Using flows

I have the same question (0)

All responses (18)

Answers (3)

v-micsh-msft on at

Like (0)

Report

Hi @michowl,

Just from the error message, I think this error should be related with the previous action. If one of the previous action failed, the following action will not be executed.

Would you please share the whole flow here?

To perform an easy test, please try to put the Excel Deparment in the Object Name part, and specify the Outlook user Profile Deparment (or some string value, better with the one listed in Excel) in the Value part.

Then check to see if this would work.

Regards

Was this reply helpful? Yes No
michowl Microsoft Employee on at

Like (0)

Report
The flow is a bit long to screenshot here, but here's the flow id: 5f542d6f-a051-4fcf-ab85-7c4f0a1f4e48

The User Profile department will always be longer than the Excel Dept. The Excel Dept is just a keyword.
However, I tried your idea (IF Excel Dept contains "ABC") and the failure remains the same with the same message.
I should also note that the flow ran just fine several days before the error began appearing.
The condition appears to be fine as well: the Condition is green checked. But the loop is red marked. Is there a way the loop itself could be failing?

Here are the outputs from the most recent failed run (before testing your idea), where you can see the Department strings
Office 365 User Profile
INPUTS
User
janedoe@fake.com
OUTPUTS
User id
[id...]
Display name
Jane Doe
Given name
Jane
Surname
Doe
Email
janedoe@fake.com
Nickname
janedoe
Business Phones
[ "+1 (555) 1234567" ]
Account enabled?
true
User Principal Name
janedoe@fake.com
Department
ABC Acronym Dept US
Job title
Jobby Job
Excel Get Rows

INPUTS
File name
/dynflow/leads routing.xlsx
Table name
Table1
OUTPUTS
value
[
{
"@odata.etag": "",
"ItemInternalId": "72eAmwnLDL8",
"Department": "XYZ",
"Owner_x0020_Email": "johnsmith@fake.com",
"__PowerAppsId__": "72eAmwnLDL8"
}, {
"@odata.etag": "",
"ItemInternalId": "3Z8NC0kLOxw",
"Department": "ABC",
"Owner_x0020_Email": "billjones@fake.com",
"__PowerAppsId__": "3Z8NC0kLOxw"
}, {
"@odata.etag": "",
"ItemInternalId": "OxFJplfMqQY",
"Department": "MNO",
"Owner_x0020_Email": "annbates@fake.com",
"__PowerAppsId__": "OxFJplfMqQY"
}, {
"@odata.etag": "",
"ItemInternalId": "CGVE8W-ujP0",
"Department": "Dummy",
"Owner_x0020_Email": "dud@dud.com",
"__PowerAppsId__": "CGVE8W-ufsd"
}
]

Was this reply helpful? Yes No
michowl Microsoft Employee on at

Like (0)

Report

i went ahead and assembled a series of screenshots to show the whole flow. (The two conditions near the top just check for empty fields and terminate the flow if true.)

Was this reply helpful? Yes No
v-micsh-msft on at

Like (0)

Report

Hi @michowl,

Thanks for the update.

I will test this from my side and share the results here.

Previous testing for the condition works at my side, I will follow your screenshots to configure the Actions this time.

Regards

Was this reply helpful? Yes No
masisley on at

Like (1)

Report

Hi @michowl,

I believe everything is working as expected here. I created a similar flow that has failure in a condition inside a loop:

You can inspect the inner actions to see what happened and cycle through the iterations with the Show run pane at the top. Likely one of your requests to Dynamics failed, which causes the entire Apply to Each scope to fail. Since these requests run in parallel, it could be that Dynamics chokes when it receives many requests at once. Once we know the failure, if it looks like a problem on our side we can potentially involve the connector team/Dynamics team in the investigation.

The reason that the display looks like this is that the first iteration didn't meet the branching condition. If it had, you'd see a red exclamation mark in the "If Yes" section.

Let me know if you have any more questions/my explanation isn't clear.

Best,

Mark

Was this reply helpful? Yes No
michowl Microsoft Employee on at

Like (0)

Report

@masisley Good to know that the for each requests run in parallel. Good design decision.

However, that should not cause the issue. Only one iteration of the loop should pass the condition and call Dynamics. Further, there are only 4 rows in the table, so I doubt the D365 Web API would fail with such a light workload.

I'll try recreating the flow from scratch to see if the problem persists

Was this reply helpful? Yes No
Verified answer

masisley on at

Like (0)

Report

If only one request is reaching Dynamics, then you should expand the action and navigate to the iteration that should have issued the request, as I did in the screenshot I attached (In your case, expand List Records). You'll likely see a more interesting error. If you don't, expand the other two actions that follow it.

Was this reply helpful? Yes No
michowl Microsoft Employee on at

Like (0)

Report

~~That's exactly the problem. As you can see in the original post, I cannot view any further detailed information in the flow run.~~

Was this reply helpful? Yes No
michowl Microsoft Employee on at

Like (0)

Report

Foot in my mouth. I guess I didn't click far enough down. I am able to view details of the Dyn calls and found the error. *facepalm*

Was this reply helpful? Yes No
masisley on at

Like (0)

Report

Ah, excellent - Hopefully the error was enlightening 🙂 Let me know if you have any further questions.

Best,

Mark

Was this reply helpful? Yes No