Loïc Mathieu

Exicode 137 means that something sends a SIGKILL to the container, so the container was killed by Swarm. You should look at Swarm to understand why it kills the container...

Ok, let me know how it goes. Do you use webhook With Post http method and a payload? We discovered a bug in a library we use and fixed it...

When using `server-type: full_content` the request is fully loaded into memory, including all multipart parts if any, so it cannot be more than 2GB, I strongly advise to set it...

@johnkm516 thanks for the additional information, it'll be helpful

@johnkm516 I tried to reproduce the issue by adding multiple triggers that, each 3s, will generates 100 flows with an input. I'm using this flow that 1 replicate 5 times...

How much executions are you created per hours? How much CPU and memory the webserver have (and replicas if you start it more than once).

@johnkm516 thanks a lot fo all this information.

@johnkm516 very interesting! Can you check if you have some logs on the server at the time of timeout (or close after). You may search for `broken pipe` message or...

@johnkm516 no, we cannot reproduce it on our side.

Hi @johnkm516 we made a bunch of fixes and improvement that may impact memory usage in latest 0.19 version. Can you give feedback whether or not you still see these...