First off. Really great tool.
Loving it as a self hosted integration solution.
I wanted to share some production experience. Perhaps someone has found a good solution.
Filter for failed runs:
In production I’m counting 45,000 executions. If an execution fails it’s not easy to find the failed execution unless with this workaround:
- set up general alert email and include the execution-id in the mail.
- Load workflow executions (which loads slowly given 45’000 runs)
- open any execution
- change the execution-id in the URL directly and load
A way to filter for failed executions or set date filters would be great.
This brings me to my 2nd question
Loading workflow executions is relatively slow and I guess it wont get better as the number of executions increases.
Is there a way to improve that?
Different backend db?
Dev / Staging / Production: Deployment via code.
I was missing a simple way to be able to deploy nodes like code to different environments (dev/staging/production).
There is an import function but it imports the nodes into a new workflow.
It’s also hard keep track of the workflow-id.
Once in production and you encounter issues, it’s very tempting to live adjust the workflow.
That would be ok, but I couldn’t find an easy way to “downcopy” the changes from prod to staging/dev.
Just wanted to share some experiences from prod.
PS: Oh if in doubt if a change has been applied to the live workflow. Restart the n8n service.