I have a lot of triggers fire every minute… I don’t need to keep the execution in the history, because most of the time it’s just a check of the database for example, it’s not an execution
Having these option + the timeout option
For each trigger make more sense, and make it easy to manage when having multiple automations inside the same workflow
My use case:
Keep the execution history clean, and only save the execution of the triggers that matter.
I genuinely think this is a great idea, if they can add a node that is basically "If workflow hits this node, “add X minutes” so that execution can count as a certain amount of time saved.
By using it as a node, you could have complex branching paths where some may have saved 2 minutes, and others that saved 30-40 minutes because of steps involved. I feel like those that use AI nodes would also love that option as it could allow for them to better assess how much they are using on particular workflows.
This can be done currently if one has access to execution data (and saves every run to track manually!). Or by sacrificing One “Super Workflow” that is home to just triggers and activates other work flows. This would be a little cumbersome to have a potential dozen workflow triggers, but then it could be left on unsave (aside from errors) and then only when a flow hits a set point activate a workflow that does track time,
I think the first comment is another use case, also valid, and chip in here to support the main suggestion: Make the “save/do not save workflow” condition on the trigger, not the workflow itself. Or give trigger nodes the ability to override the workflow setting.
My use case to similar to OP:
I have a workflow with a webhook, and a 5-min scheduler.
I want to save all executions from the webhook, but only failed execution from the 5-min scheduler.
