Since (quite) a few days several advanced flows are reported as being broken. Sometimes 2x per day, sometimes 4 or 5 days apart. Usually they are the same 4 to 7 flows. But not all advanced flows. I have taken quite some time to check those flows, but I never see anything wrong with any of the flows.
Does Flow Checker somewhere make a note/log why it thinks a flow is broken? So I can investigate what is going on?
Found a minor (but annoying ) issue, in the flow checker settings when trying to open an Advanced Flow (ctrl+click), it won’t open as the URL is slightly different from a regular flow
an additional /advanced, IE:
Hi @martijnpoppen , another challenge for you and your fantastic app Do you think it would be possible to report such broken flows ? Something has happened with those conditions marked (we discussed in the relevant app thread) and flow are broken - but it’s not reported and the flow itself almost do not indicate any problem until launched / tested - then it throws error :
@Sharkys floechecker wont see those cards as broken as they still have a value. However that value is not in the manifest of that app.
I could check if a flow could be tested. Theres a option for that. Not sure if that will fix it.
Thank you Martijn, just in case it makes sense actually. Not sure how many such broken flows could appear for others as it’s linked with specific app / development change that triggered that. So if it’s unique, it is probably not worth the effort. Richard already explained how this happened …
Yep, with 200 devices it’s not so bad ratio Still waiting for some option for “easy” migration from Flows to AdvancedFlows, so that I would not have to copy everything and every flow manually. But true is I need to start optimizing, as I’m not over yet
Indeed, but this was un-intended error, already fixed in the meantime, after I realized actually what one of the user wrote, I think at that time also developer realized it as well… it’s already fixed in the next version, yet - it’s pretty un-detectable/nasty error . Possibly also something that would/could be addressed by Athom as maybe that should be prevented “by design” but not an expert here … anyway, maybe will not happen again (like with other app, other developer).
** update ** … I checked again, it’s not fixed yet, I will fix it manually then.
Sounds good! Maybe this is optionally possible as well (just nicetohaves): if a flow is triggered more than X times in the last X s/m/h/d, then... if a flow was triggered more than X times (whenever), in X s/m/h/d, then...
The last one is to filter on ‘busy’ moments in time