did I say something? Can’t recall 
Thanks a lot! It’s incredible how quick you always are 
New app update (test: 1.10.1.):
- NEW: add Flow Utilities support
- NEW: improved functions for finding broken FlowTokens
- FIX: update app ID for Flow Utilities after Breaking change
Together with @RobbertV I build a new app. This will add Flow Utilities and adds some useful tokens to use. Now FlowChecker can also find these tokens if they’re broken
I really like the app, already found me some broken flows several times, with over 800 flows it is bound to happen.
I did find one thing with the “Turned off flows” overview (app’s settings) though (probably all, but didn’t have any broken flows yet with this issue).
I use the < bracket in my flow titles occasionally (when I use “is less then…” logic in the particular flow), seems like the overview page doesn’t really like that as it really messes it up (yay for HTML characters!), probably needs some escaping.
@Caseda
Thanks! 
Ah nice find!
Yep it’s just parsing HTML and putting the names in pain text.
Will make a fix for that!
Yes, that works brilliantly now 
thanks ones more for the quick fix.
I gues it has to be connected to the bracket (IE: <example, not < example), html code it also needs to be connected to work.
Nice, Will push it to live @Caseda 
New app update (live: 1.10.2.):
- FIX: < and > causing settings page to break.
I really like your app Martijn. It saved me more than once. But I’ve also a request/questions
Sometimes I’ve a flows that is starting an other flow (with start a flow) but see now sometimes flows that don’t exist anymore. So when you test the flow I’m getting a message that it won’t work.
If its possible, it will be really handy to implement it into flow checker.
Thank you!
New app update (test: 1.11.0.):
- NEW: ADD unused flows (+settings and flowcards)
- NEW: ADD unused logic variables (+settings and flowcards)
- NEW: ADD flowcards for enable/disable interval
On request of @Peter_Kawa I added unused flows and logic variables.
Unused flows: Any flow which has a unknown trigger or a ‘This flow has started’ trigger (e.g: Gedeelde Flow | Homey)
Unused logic variables: Declared logic variables which are not used in any flows
Screenshots of new features:
Flowcards:
The world record holder in improving apps. 
Super cool again, Martijn Verstappen 
How nice to see the “unused logics vars” and “unused flows”
scripts have been integrated.
To be able to en-/disable the interval checker using flows is neat!
Cheers
Sorry, but I had to donate little bit again 
…sent.
@martijnpoppen I wonder, for Unused flows, what about those triggered manually ? I wonder if we can’t exclude them or have setting to exclude them… but true is, I found some of them I can probably delete thanks to your latest update. Yet it would be more interesting to see those triggered by some condition but never actually running… just idea/opinion, I can live with what you already did
@Sharkys thank you very much! Appreciated!
I think I can split those in to 2 sections.
Will look into that
Good Q @Sharkys.
“Unused flows” is a bit tricky description @martijnpoppen (and it’s my fault 
).
I’d like to suggest “No trigger & Not started from other flow” as description. But it’s tooooooo loooooooong heheh.
True unused flows have a counter below 1 I would say.
