Http request - after x amount of calls crashes n8n

Hi @Kool_Baudrillard, I am sorry you are having trouble.

This does indeed sound like a memory problem.

Any chance to get rid of the previous responses to keep it performant since I would like to run it over night an have xK of calls?

Yes, that’s possible in most cases. If you do the heavy lifting in a sub-workflow and only return a single result item (something like { "success": true }) to the main workflow the memory consumed by the sub-workflow would become available again.

Check out Channel closed Error - #3 by MutedJam for a recent example and please do let me know if you have any questions on this.

2 Likes