Automation turned itself off
Is there something which would cause an automation to turn itself off? I built a new automation that adds X child records when a button is clicked, where "X" is number field on the parent record. ...
Forum Discussion
MarkShnier__You
Qrew Legend
Qrew LegendBut I cannot find any documentation on this I strongly suspect there is a limit of 100 loops in an automation triggering itself. They probably try to protect the automation from getting into an infinite loop. The automation may have disabled itself although I would've thought it would have recorded an error. Do you see an error count in your list of automations?
One idea would be to convert this to a Pipeline as it may have higher limits.
------------------------------
Mark Shnier (YQC)
mark.shnier@gmail.com
------------------------------
One idea would be to convert this to a Pipeline as it may have higher limits.
------------------------------
Mark Shnier (YQC)
mark.shnier@gmail.com
------------------------------
- Hi Mark - no there was no error message showing in the "Error count last 7 days." My colleague just noticed it eventually stopped counting down and then when he tried to use the button for other records it now longer worked. I also thought it might be thinking it was in an infinite loop and therefore shut itself down. I would have also expected an error message though.
We'll probably just try running numbers less than 100 and doing it in two steps in the interim. Not having to click the button 100 times is in itself a big improvement. It is rather unusual that we would need to have the number that high. Probably 75% of the time we only need one child record added, 20% of the time 2-10 child records, and only the last 5% that are bigger numbers.
I do want and need to figure out Pipelines, I've attended a few trainings, but it just hasn't clicked enough for me to get my own to work. (I haven't tried the "start migration" but I know that need to do so.)
------------------------------
Kim G
------------------------------
