Cannot delete a running execution anymore?

Feedback
1

I was able to delete executions in certain scenarios and it was working fine, but now, after an update I’m getting errors in previously working workflows. I know that I can set global variables to delete executions. But I want to control this manually as well. Is the solution to create another cleanup workflow, that will take the execution number passed from the workflow that needs to be deleted?

The n8n node give an error “Cannot delete a running execution”. It makes sense, but I liked the way it was working before. The deletion was the last step of the workflow. Ideally I would like the n8n node to have a “delete the current execution” option.

This was working before

image
image1994×772 73.2 KB

But not anymore :frowning:

image
image1654×1178 97.5 KB

1 Like
2

I tried creating a separate workflow, it’s failing too :frowning:

image
image1744×664 181 KB

I even tried to put a 10 sec wait node, still failing with the same error

image
image1398×432 81.2 KB

Seems the delete execution node has become useless

3

Hasn’t this affected anyone else?
I was deleting lot’s of executions, which didn’t have any value for me, making everything much cleaner. I feel like I’m drowning in useless executions now, having to search for the important ones.

4

It’s affecting me as well. I desperately need a way to stop an executionm, and I thought deleting would work