I have a workflow with a multi-step function that uses python to split a PDF into single-pages, upload the page to Retool Storage, and insert a record into the Retool Database.
When I run this interactively in the editor, it works every time.
When I trigger this via webhook (with the exact same inputs), it fails every time with Code 139 / memory.
Does the workflow backend have a different environment / specs when running in the background vs interactively (in the editor)? How can we troubleshoot this? I’m working with small files (1-2 mb).
Hey @mrgoynes - thanks for reaching out! When you say that your workflow is successful when run interactively, are you executing individual blocks one at a time or hitting the Run button in the top right of the editor window?
The documented workflow limits do not apply in the former case, but the latter is equivalent to running the workflow on a schedule or triggering it via webhook.
Ah, I see. This is helpful info. I have been running interactively block by block.
Is there a way to analyze & tune how much ram a block is taking? I would prefer to keep my worfklows completely in Retool, but if I can’t get through a few python tasks before hitting the limit, it’s a deal breaker.