Impossible to trigger the next workflow

[MutedJam]

Here is an example consisting of one parent and one sub-workflow:

Channel closed Error

Glad to hear you figured out what was wrong here @Edmunds_Priede, thanks for confirming! n8n can be quite memory hungry as it has no built-in limits when processing large amounts of data. If it’s mostly n8n consuming the memory on your system, it can be worth reducing the amount of data processed in a single workflow execution. A quick example on how to address this in n8n: I was working with a user who had trouble importing all Google Calendar events the other day. In such a scenario it could…