So I have a workflow I’ve been developing for the last few weeks, and it’s been generally working like a champ.
However, today I encountered an unusual error when running an event through it. This error occurred in a step which has been working and I haven’t changed recently, which has me concerned. Can someone help me understand what caused this error?
getaddrinfo ENOTFOUND
at GetAddrInfoReqWrap.onlookup (dns.js:67:26)
I did some brief web searching, and it sounds like a DNS issue. This occurred for a few minutes around 2:30pm CDT (UTC-5).
How is Pipedream configured for DNS resolution?
Is this something that Pipedream’s SRE team would want to know about so they can change some configuration to mitigate the likelihood of this error occurring?
@chexxor and I chatted about this over Slack. DNS resolution is provided by AWS in this case, and is actually abstracted from us. It’s possible they had an internal hiccup, but generally DNS resolution should work well (we’ve historically observed no major issues here).
If anyone else observes issues with DNS resolution within workflows, please let us know and we can look into it.
Hi @russkiimike , would you mind clicking the Share button at the top-right of the workflow and share it with dylan@pipedream.com? I’d like to take a look.
In the popup that appears, replace the value of admin_api_url with the API URL from step 2.
Try to create the source again and let me know if you see the same ENOTFOUND error, or a different error.
I believe this error is related to us not being able to resolve the URL you provided there, so I’d like to see if that fixes it.
I noticed another issue with the event source that we’re tracking here - you may see that error when you create your source. Please follow that issue for updates about that. We’ll get someone on that ASAP.
Getting a similar spurious error on workflows, randomly it works:
(From http step)
Error
getaddrinfo ENOTFOUND api.sms4free.co.il
at null.__node_internal_captureLargerStackTrace (internal/errors.js:412:5)
at null.__node_internal_ (internal/errors.js:634:10)
at GetAddrInfoReqWrap.onlookup (dns.js:71:26)
(http)
Sometimes it does work after replaying the payload.