This topic was automatically generated from Slack. You can find the original thread here.
Guys why does a Pipedream internal error appear? it does not help me at all at debugging the current issue. I am seriously considering canceling this service if there are going to be these obscure error messages that do not indicate where to look or find an answer.
Hi Dulcidio,
I totally understand your frustration with this error, it’s bitten me a few times as well.
We’ve just published a general troubleshooting guide here:
Unfortunately, this error is being thrown from AWS Lambda itself. And the platform itself isn’t providing a trace either. So this is the most granularity we can give unfortunately.
We will be linking to this guide from the error banner, and will be updating this guide with more causes and corresponding solutions as we come across them.