What Could Be Causing Out-of-Memory Errors in My Workflow Despite Most Triggers Not Going Beyond the First Step?

Bugs
1

This topic was automatically generated from Slack. You can find the original thread here.

I got a lot of out-of-memory errors over the weekend on one of my workflows. The first step of this workflow is a validation step that ends the workflow for triggers that do not meet a certain condition. When I reran a few of my events that had the out-of-memory error, most of them triggered that first step. So I’m trying to figure out why they would have run out of memory if most of the workflow didn’t even run.

This is a v1 workflow that has been running without issues for a while. I did make a minor edit to one step on Friday, but it doesn’t seem like the kind of change that could cause memory issues, especially since that step is not reached in most runs of the workflow.

Any ideas on what could be going on here?

2

Hi Celeste,

v2 workflows were released in April 2021, and no future updates are coming to v1.

We highly recommend upgrading to v2, and you can follow this guide to learn how to: Migrate from v1

v1 workflows also automatically deployed during editing, which will trigger updating packages, so it’s possible that new NPM packages are causing the memory issue.

In v2, you can pin specific versions of packages to prevent broken updates.