CPU/Memory Limit error message
Hi,
I was testing the workflow and performing some heavy tasks (really intensive ones), and occasionally encountered the error:
"The step crashed the worker (or exceeded CPU/Memory limits) during this attempt."
This error occurs in certain steps, but since most steps follow the same function with different arguments, it doesn't seem to be an issue with the function itself.
The primary challenge is that the error message doesn’t specify whether the issue was due to exceeding memory limits or CPU time limits. This lack of clarity makes it difficult to diagnose and optimize the code effectively.
It would be greatly beneficial if the error message provided precise details about the cause of the crash—whether it was due to memory usage or CPU time limits. Such information would significantly aid in troubleshooting and improving the performance of the workflow.
1 Reply
I do understand where you're coming from, and we'll try to do this better in the future 🙂
We already distinguish between CPU/Memory errors but sometimes, the error propagated to us is generic (and a bit unreadable) - so we know that your Worker crashed but, we don't know why the Worker crashed, since the error message
you can also look in dash/workers logs to see why the worker crashed 🙂