many flows failed without me triggering it

(0) Share

Report

Posted on by Sifu

834

hi guys,

i have a parent flow which based on user selection will then run a particular child flow. The parrent starts on new item in list is created. It will also pass on to the child the item nr so the child has something to work with...

Today on monday i see that there are quite few child flows that are failed, and start shoudl be yesterday... but no one has started anything yesterday. I can see the item id that was passed to the child, but that item does not exist (the list is empty...)

Any idea why?

Categories:

General topics

I have the same question (0)

All responses (11)

Answers (0)

AS-06081019-0 1,736 Super User 2024 Season 1 on at

Like (0)

Report
Copy link

Link copied!

@Sifu Could you please revisit the trigger condition.
Also, as a workaround for next time try with a condition in modified flow verifying if the Created field is not equals Modified field, if this condition is false the flow starts.

Was this reply helpful? Yes No
Sifu 834 on at

Like (0)

Report
Copy link

Link copied!

hi, @Ankesh_49 , cant follow what could be wrong with this trigger, i suspect that the issue is because i cleared the list, on the other side it should not matter since the trigger is not on modified...
Q1: what should i change?
Q2: i could change it all to if item is modified but whats the idea behind if the additional condition will create "when item is created" from it...

Was this reply helpful? Yes No
AS-06081019-0 1,736 Super User 2024 Season 1 on at

Like (0)

Report
Copy link

Link copied!

You could try changing the trigger condition:
AS: The idea behind additional condition is to make sure that the flow is not performing a run for any update, it will check for a particular desired update for which you want it to run.

Was this reply helpful? Yes No
Sifu 834 on at

Like (0)

Report
Copy link

Link copied!

i see, that suggest however that i configure this on the child since the parent looks ok but the child looks like it started without a reason... i have however no clue what the condition could be/look like

Was this reply helpful? Yes No
AS-06081019-0 1,736 Super User 2024 Season 1 on at

Like (0)

Report
Copy link

Link copied!

@Sifu refer this https://www.youtube.com/watch?v=j-gP-E6CCE4 as it will give you an idea to design your trigger condition for child flows.
https://thrivenextgen.com/microsoft-power-automate-flow-trigger-conditions/

Hope it helps

Was this reply helpful? Yes No
Sifu 834 on at

Like (0)

Report
Copy link

Link copied!

thanks, had a look , its now a bit more clear... but, do you know why the flows started at all? When i do some conditon i will need to test it, since i am not sure what caused it it might be difficult to know if that works as desired

Was this reply helpful? Yes No
AS-06081019-0 1,736 Super User 2024 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Any forced deletion of item lists?

Was this reply helpful? Yes No
Sifu 834 on at

Like (0)

Report
Copy link

Link copied!

well i removed / cleared the list... so yes, but if i removed one random item now i dont see that it started again, something... could it be that its related to items that are still running (cant they be removed)

Was this reply helpful? Yes No
Sifu 834 on at

Like (1)

Report
Copy link

Link copied!

alright, so i think i understand it now a little better, the situation is as following:
1, new item gets created
2, that triggers parent flow
3, parent starts child
4, i remove the item because tests are over
5, child flow had set expiration and steps to do after expiration and wants to continue
6, parent will notice that flow was terminated and starts it again, makes many retries...

so i think that the condition should be set to parent, if any at all...because in production environment i will not delete anything...

Was this reply helpful? Yes No
Sifu 834 on at

Like (0)

Report
Copy link

Link copied!

@Ankesh_49 so just for future generations i like to capture the workaround...
what i missed was also that if you run child flow you have to finish with respond to workflow/powerapp or else it will try to run it again....
I configured one get item to figure out in what state is the item (this runs if approval expired)
followed by the respond to workflow/powerapp (run if get item is failed)
followed by termiante (run if respond to workflow/powerapp is success)
followed by other step (run if termiante is skipped... kind of normal process that continues...)

To be sure i also created one column where if flow starts it will record "1" but default value is "0" and added condition:
equals(triggerOutputs()?['body/mycolumn'],0)

Was this reply helpful? Yes No