@netroy Thank you very much for your response, I have already contacted the support team.
I’ll still ask you a question:
Are these types of problems common in Cloud? Since at no point is it mentioned that you have to take into account the memory or size of the executions.
I think out-of-memory issues aren’t that common anymore, because most people on the starter plan often don’t have that much data in their executions.
However one scenario where they do happen is when it’s a manual execution and there is a lot of data, because all that data is currently buffered in memory to be sent back to the client over websockets. This can often increase the memory usage significantly.
You could try to activate the workflow, and try executing it via the production webhook url. If you still see the crash, we can try to debug this together.
Not saying that you should not use manual executions, just that 320MB of memory on the starter plan can often be too low for some workflows.
In cases like these, people can either break up the workflow into sub-workflows, or upgrade the plan to a higher memory tier.
