Hi,
We have been calling several AWS Lambda’s from the AWS Lambda Node, and we recently have seen this error: Platform Error - Error Code 0x101
Any idea what causes this and could be something we are doing? This only started today, and we do not think we have seen this error before.
Thanks,
Stephen
Stephen,
We took a look and it seems like starting yesterday around 5pm EDT we are getting occasional DNS errors resolving lambda.us-east-2.amazonaws.com - which results in the error you are seeing in the workflow node. We are currently digging in further to see what the cause is (as we don’t seem to be having DNS issues elsewhere, and it is only a fraction of a % of the usage of that node that is seeing the error). Thanks for bringing it to our attention!
Hi - as of this morning, we were still seeing this platform error - any insight on your side why this is happening?
Thanks in advance,
Stephen
We still don’t have a clear cause of the problem; we’ve restarted a couple of the workflow runners where the error occurred, but the fact that it’s not localized to a single runner means that’s unlikely to resolve the issue. We may be PM’ing you for more information as we try and hunt this down. Thanks for the information you’ve provided so far.
Hi, a quick update:
Not sure if you did anything on your side, but we replaced the certificates for both of our custom domains, and we have not seen the error for 24hrs now. Replacing the certs does not feel like that should have corrected this issue, but maybe that did something??.
Stephen
We did make some changes on our end to adjust our DNS lookup code this morning and have not seen the error since.
While we did see the error occur a couple times yesterday evening, neither of those were from your application. We haven’t seen the issue in your application since about 2pm EDT yesterday … Was that around the time that you made the changes on your end?
“Was that around the time that you made the changes on your end?”
Yes, that was about the time we replaced our certs.
Well, that didn’t last 
We just had the same error, so nothing we did fixed it.
Regards,
Stephen
Just letting you know we’re still looking into this. I will keep you posted. Thanks for your patience.
While we still haven’t found the underlying cause of the issue, we did push out a fix yesterday that will drastically mitigate it.
When running the Lambda Node, if we receive the DNS error you reported, we immediately try invoking the node again. So far this has held well; we’ve seen the DNS error come through but the second attempt has always worked. So the good news is, if the node was working 99.9% of the time previously, we believe it will work about 99.9999% of the time with this fix in place 
.
We’re going to continue monitoring this and see if we can isolate the cause, but hopefully this mitigation step will all but resolve the issue.
Thanks again for your patience and your help in tracking this down.
Hey Dylan,
We are receiving same error Platform Error - Error Code 0x101 again from AWS lambda nodes. To be precise, most of these errors are produced around 5 pm CST at a random day / sometimes consecutive days. I can give you more information if needed. I am replying to this chain because this thread was initiated by our previous engineer stephen with same error message.
Regards,
surya
Hi, yes, more info would be helpful.
- Links to workflows / custom nodes where the error is occurring
- How many errors are we talking here? Is this failing constantly? One out of every 100,000 runs
On my end I’ll ask the engineering team for any info they can provide.
Hi Dylan,
Thanks for the quick reply. Here’s the info:
Workflows / nodes affected:
- Flow ID — 6297cc98d33740be226284a6, Node ID : uKfU7meFLj
- Flow ID : 6297cd1b28849eea29392ecb, Node ID : 1AnbhXKhow
- Flow ID : 6620116f9504f43c223a0276, Node ID : BuQTEj2wCt
Frequency: Per Workflow Metrics over a 24 hours: 6 errors out of 698,300 completed runs — roughly 1 in 116,000, so in the ballpark of the “1 in 100,000” rate you mentioned. Not constant/blocking, but recurring at a low steady background rate.
Regards,
surya
Thanks, this is helpful. It is indeed a very low failure rate but we’d like to figure out what’s going on regardless.
I see that you have another Lambda integration in some of these flows pointing to a dev environment, though that dev environment is also in us-east-2. Do you ever see failures when invoking the dev Lambda node?
Thanks, No failures reported with Dev AWS Lambda node. Dev environment has only few number of devices that report and throughput is very less compared to that of prod.
FYI : Just now I received 14 error messages during AWS lambda insertions for the Flows mentioned above with “Error Code 0x101” .
Thanks. We saw that same issue hit our error tracking software. I’m reporting to the platform engineers.
Thank you so much! awaiting response.
Hi Dylan,
Yesterday (07/15/2026) we have received around 50 Timeout errors (Error Code 0x101) in between 11 pm cst and 12 pm cst. Would like to know if there is any fix coming our way which resolves the issue.
Regards,
Surya
We caught those errors as well. Our platform team is looking into this today.