You can only start another simple flow that starts with a âwhen this flow is startedâ card, or a âwhen this flow is started with a (number/boolean/text/image)-tagâ card. Or you can start another advanced flow that either has a start button, or at least one âwhen this flow is started with a (number/boolean/text/image)-tagâ card, or a start button.
In both cases the flow will start from that point and will include the variable that you pass on as a tag that you can use in the flow.
If you want to start flow XX from another flow with âstart flowâŠ..â flow XX has to have a âstartâ-button. Otherwise it isnât listed in the possible choices.
Similar with the âstart flow ⊠with a tagâ. Flow XX has to have a WHEN-card â this flow was started with a tagâ
Ah, Thank you for pointing that out. That is a little grey area I didnât knew about. I tested it, but I would not recommend using it this way as it is very tricky. You could for instance use the âWhen Luminance is changedâ card as a starting point, and it is trigger-able. But as soon as you actually use the Lumince value tag in your flow it isnât trigger-able anymore.
I would just recommend to always start with either a âwhen this flow is started (with tag)â card, or a start button and connect those to a âandâ card or a âthenâ card.
indeed, very shady business actually. It is very easy to break something in another flow without you actually realizing it. Iâm surprised that Athom implemented it like this.