# \[FeatureRequest\] Default error flow-card handling **URL:** \ **Category:** Ideas & Suggestions\ **Tags:** featurerequest\ **Created:** [July 23, 2024, 9:22am UTC](https://community.homey.app/t/featurerequest-default-error-flow-card-handling/113305 "2024-07-23T09:22:49Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Articate](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/articate/32/57311_2.png) [@Articate](https://community.homey.app/u/Articate)\ **Post date:** [July 23, 2024, 9:22am UTC](https://community.homey.app/t/featurerequest-default-error-flow-card-handling/113305/1 "2024-07-23T09:22:50Z")
I’ve set up manual error flows for errors I suspect might pop up. However, I’d like to be able to set a default flow-card for all error-outs of all flow cards. As a user I want to be able to set a default error flow card, so that any card that has an error-out, but I haven’t attached anything to, automatically uses the default. Conversely, any sort of default error handling in flows would be useful. I’ve had some weird errors pop up in the past, and I could only see what the error was, because I realized a flow wasn’t working, then testing it manually and seeing where it failed. ---
**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\ **Post date:** [July 23, 2024, 10:25am UTC](https://community.homey.app/t/featurerequest-default-error-flow-card-handling/113305/2 "2024-07-23T10:25:04Z")
Use the Simple Log app in the meantime > [@\[APP\]\[Pro\] Simple (Sys) LOG - Use this app for Simple (Sys) Logging](https://community.homey.app/t/app-pro-simple-sys-log-use-this-app-for-simple-sys-logging/77533): > > Simple (Sys) LOG [Live now](https://homey.app/a/nl.nielsdeklerk.log/). The new and improved Simple (Sys) LOG. This app makes it possible to add logging and/or notifications to your Flows. Optionally a log can have, next to it’s message, an App/group, severity and facility/category. Connect to a Syslog You can also connect to multiple Syslog-clients to a) send specific message and b) have all default messages (with certain severities or higher) send there. New App Settings: Syslog interface This new version saves the logs int… Script to add log cards (also error cards) to your flows in one go: > [@\[APP\]\[Pro\] Simple (Sys) LOG - Use this app for Simple (Sys) Logging](https://community.homey.app/t/app-pro-simple-sys-log-use-this-app-for-simple-sys-logging/77533/6): > > Script to automaticly include Simple Logging cards into your flows Use this script to automaticly add logging cards to your (advanced and normal) flows: It adds logging to each flowcard’s error catch in advanced flows. Also it adds cards to the triggers (WHEN), conditions (AND) and actions (THEN). It will generate one Automater flowcard in each flow. This card can be used to configure each flow on it’s own: Update: When you set this to No, the Autmoater card itself will not be changed when … ---
**Author:** ![RonnyW](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ronnyw/32/10879_2.png) [@RonnyW](https://community.homey.app/u/RonnyW)\ **Post date:** [July 24, 2024, 5:29am UTC](https://community.homey.app/t/featurerequest-default-error-flow-card-handling/113305/3 "2024-07-24T05:29:03Z")
You can also use sub flows. This is especially useful when you have several triggers and one Action process behind. You can put all actions and conditions into one flow. Then make another flow with all triggers. Then start the flow with the logic card “start flow with number argument” if you want to pass a trigger value into the second flow. This way you only need to use the error output of the “start flow” card to catch all errors that can occour inside the second flow. ---
**Author:** ![Articate](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/articate/32/57311_2.png) [@Articate](https://community.homey.app/u/Articate)\ **Post date:** [July 24, 2024, 1:11pm UTC](https://community.homey.app/t/featurerequest-default-error-flow-card-handling/113305/4 "2024-07-24T13:11:51Z")
> [@Peter\_Kawa](#): > > Script to add log cards (also error cards) to your flows in one go: Well, that’s a handy solution! Thanks for the tip. > [@RonnyW](#): > > This way you only need to use the error output of the “start flow” card to catch all errors that can occour inside the second flow. That’s a clever way to do it. I’ll certainly think about applications for this. ---
**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\ **Post date:** [July 24, 2024, 3:49pm UTC](https://community.homey.app/t/featurerequest-default-error-flow-card-handling/113305/5 "2024-07-24T15:49:56Z")
Another interesting app to check out, will be [Audit](https://community.homey.app/t/app-pro-audit/101554) ---
**Author:** ![Articate](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/articate/32/57311_2.png) [@Articate](https://community.homey.app/u/Articate)\ **Post date:** [August 14, 2024, 8:55pm UTC](https://community.homey.app/t/featurerequest-default-error-flow-card-handling/113305/6 "2024-08-14T20:55:13Z")
> [@RonnyW](#): > > You can also use sub flows. This is especially useful when you have several triggers and one Action process behind. I tried this, couldn’t get it to work. I don’t want to start the mood “Night” unless all relevant windows and doors are closed. So I have my Night flow: When flow starts → Then Start flow “night-test” → Then set mood Night The idea is that Start flow would fail, since night-test now has a HomeyScript that’s simply: `throw new Error("Can't set Night mood");` It generates an error. But on the outside, that error isn’t seen on the “Start flow” card. The idea here was that when conditions weren’t right, I’d throw an error to disrupt the flow from the “Start ‘night-test’ Flow” card, so it didn’t actually set the mood. Figured I’d check that I had the idea right. What I’m trying to achieve is to have a “And Flow returns true”, so I can break down this Night flow into smaller parts, where I don’t continue the main flow unless the checks are right.