How Can We Fix the Out of Memory Error at the Start of Workflow and Does it Consume Credits?

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

:wave: over the past few days I got a bunch off out of memory error just when the workflow starts.
So OoO on the cron step.
Are you aware of that, how we fix this? Pipedream - Connect APIs, AI, databases and more

BTW, are you consuming credits for that??

Hey , usually you can increase the memory limit on your workflow, then the issue should be gone.

Note that the memory limit increments will resulted in higher limit for your workflow run (which is has estimation show on the Pipedream builder UI as well)

The memory issue might typically because of the amount of data the workflow needs to process

:wave: Thanks for the feedback

as you can see in the report, it seems the OoO happens at the trigger step, so basically the workflow did nothing at all. (Total Duration 0s, Step Executed 0/6)

Thatโ€™s the reason Iโ€™m reporting that issue.

Hey , the error in trigger step is a UI bug. The workflow actually executes through the steps, but it failed in the middle with out of memory error.

Since currently Pipedream do not record the execution results for this kind of error, it shows the error failed at the trigger step.

We have this improvement for the Ui on the backlog already, but it is subjected to prioritization from Pipedream team

Ok great. Thanks for the information :slightly_smiling_face: