Do we have a "save execution" node?

Feature Requests
,
1

Hello all,

I believe there is no such node, if there is please guide me to the documentation :slight_smile:

I found myself in a position where a flow is going to be executed many times and I’m not interested in saving the executions, EXCEPT when certain things happen. For example, I have error handling in my flow and it doesn’t fail as a flow so I can’t use the general flow settings “save on fail/success” etc. But there is a certain case, if that happens I’d like to save that execution. So I thought we can have such a node and I can connect it to an IF to check whether or not the whole flow execution should be saved based on dynamic criteria.

Do you see some merit in this? Is there a way to accomplish this without a specific “save this execution” node ?

2

So a specific node for this does not exist, but it sounds like a neat idea to me.

For example, I have error handling in my flow and it doesn’t fail as a flow so I can’t use the general flow settings “save on fail/success”

What you could do for now is at the very end of your workflow, after your own error handling, place the Stop And Error node for example like so:

That way you can still trigger an error that would lead to execution data being saved, even if your workflow would otherwise ignore errors.

1 Like
3

Thanks @MutedJam , I haven’t seen this stop and error node yet. It will solve my problem for this specific use case, yet I still think “save execution” node would give much flexibility especially for debugging and legal logging cases.

4

It’s sorta implied with “when certain things happen” but to be more explicit, I would like this node to cut down on noise with a schedule trigger. When I use that to poll and see if there is any work to do, I don’t want to save all the executions where there was nothing to do, so the same logic that continues the workflow when there is something to do, could also switch on the “save execution” and everything else (the noise) could follow the current workflow setting.

As an alternative, there could be some other options in the workflow settings like “Save execution if execution time exceeds: ?? seconds”, or “Save execution when last node isExecuted”

1 Like
5

This would be super useful. Actually a “Do not Save Execution” would be even better for us.

We get a lot of “trashy” webhook calls that we would like to “filter out”, right now they are polluting the execution list and the only option is to Not save any execution at all.

1 Like
6

you can use the “Execution Data” Node to add filterable data to executions:
https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.executiondata/

With that you can at least filter your executions in the execution overview.

7

The issue is the general executions list, gets flooded

1 Like
8

I made a small hack.
This is like “Don’t Save This Execution” node.
This tiny workflow will delete given execution.
For this workflow executions save is disabled.

In workflow we want to not save we can just call this guy with {{ $execution.id }} and without waiting like this:

It works almost perfectly.
The only thing is that executions id is still incrementing.

9

@grigoreo_fox Solution has been great for deleting high frequency webhooks where we receive a lot of calls we never use.

but there’s still a missing a “Archive Execution” or “Hidden Execution” option and a Workflow setting “Do not show Successful executions in the general execution list”.

There are a lot of use cases where I’d rather not delete executions but they are so High Frequency that I’d rather not have them show up in the general list.