This topic was automatically generated from Slack. You can find the original thread here.
Please when or what triggers this to happen… I see it happen all the time…
It’s like the WF doesn’t run, like the environment starts up, but no execution is done till it times out. What could be likely causes…
(The WF isnt doing anything that will warrant increasing more than 256mb)
This error is caused by the workflow’s memory being exhausted at run time.
Perhaps a new version of an NPM or PyPI package in the workflow is causing the issue? Have you tried pinning to an older version?
It can also be memory intensive code or large events causing the issue.
Axios is the only package I am using in the workflows…. I’ve rescoped my endpoints to only get/return what I want…
Is it possible to find the exact action within the workflow that is causing this… I would have expected the error to mention this
No sorry, due to how workflows are bundled we don’t have that level of visibility.
Is the workflow using pre-built actions or triggers?
It’s using a webhook trigger
Ok, is it using any pre-built actions or are all of the actions Node.js/Python code?
Strictly node.js code
Sorry, I just remembered I have this package in one of the workflows. I’m going to remove the builder and see if anything changes…. but based on this package size, I’m not sure its the culprit
**import** { parseString, Builder } **from** "xml2js";
Workflows deploy to separate Lambdas, so memory usage by workflow A doesn’t affect workflow B.
Does the workflow with this OOM error manipulate files?
It doesnt manipulate files… I use this xml2js to parse just 1 line of xml
Hm then that library could have a memory leak of some sort.
Perhaps try pinning to an older version that was published before you started noticing this error. Or potentially try a different package.
