ok, got a few set nodes with a lot of items ^^
I am using the set nodes to remove not needed fields to help with memory requirements. I hope that’s the right way of thinking here.
I’ve also found the workflow which used 8GB of RAM on the client yesterday:
It has two pipedrive nodes which read about 600 deals at the same time and processes the data for our dashboard. (I have to split it two workflows, but thats at the moment not really easy todo: Bug node selection does not work)
When execution the workflow it uses 800MB on the Client (150MB on the Server), but as soon as the Execution finishes it releases that memory, which was not the case yesterday.
Writing another post rn, where one of my workflows got a memory problem and with it failed multiple other workflows.