For that workflow run, I'm seeing this error: "FATAL ERROR: Scavenger: semi-space copy Allocation failed - JavaScript heap out of memory", so it definitely tracks with memory issues. I also see the runtime error: exited workflow with code 139, and here is a thread on that. I've asked internally and there is a 100MB payload limit for any workflow block, so a lot lower than 1GB. While I get that ~33MB of data is lower than 100MB, I would still look into ways to limit the size of the incoming payloads.