Answered

Condition is met, but nothing runs underneath it

(0) Share

Report

Posted on by ted1

Hello,

I have a flow which says its running correctly, but doesn't actually do what it is meant to do. It was running fine, for about a year, up until the 19th January

Essentially, the flow is set to run when an Item is updated or created. The Flow gets that item, then searches for it under another list. If it returns nothing, the flow should create the item in the second list. If it finds item in the second list, it should update it.

Updating the second list works fine, it is the creation that is not working. Both branches use the same connection and the connection has the relevant access to both Lists.

Any ideas?

All responses (2)

Answers (1)

Verified answer

ted1 33 on at

Like (0)

Report

Re: Condition is met, but nothing runs underneath it

I stil don't know what caused it to stop working, but I moved the "Create Item" action so it is directly below "Yes" and it now works fine.
ted1 33 on at

Like (0)

Report

Re: Condition is met, but nothing runs underneath it

EDIT: This particular issue is resolved. I found a second flow that someone had setup incorrectly and had only mapped the Flow name to the SPList Title column. The "create item" issue above is still an issue.

A bit more info, despite the Flow saying that it is Successful and the Create Item saying it hasn't done anything, the flow is creating an item, but it is putting the trigger name in the Title field and no other data.

I have double checked all the mappings that they are correct.