Hi!
I’m trying to automate testing of several APIs saved in some collections so I have been trying to use Monitoring or Scheduled Runs in postman but they return the same error: “Error: getaddrinfo ENOTFOUND”.
When I send requests individually, it runs perfectly and returns status 200. But when I try running the Monitoring or Scheduled Runs, I see the same errors.
I have already checked the URLs are the same as the individual requests that worked. I disabled proxy in postman settings. I tried setting timeout in between them. I pinged the domain, the ping works and returns an IP address. Not sure what else to try.
Can someone please help?
Hi @aviation-observer-72. Welcome to the Postman Community 
.
Are you running these requests with environments and are the URLs stored in the environments? Can you share a screenshot of this error?
Hello, I’m also encountering a similar issue. The URL (it’s not publicly available) is for internal QA use. Also, I had the URLs added as a collection variable or in the request itself. When I run them individually, they are running successfully. However, when I schedule it to run in Postman Cloud, it fails with the above error. How can this be fixed?
Hey @supply-cosmologist-8 
Those requests would be running in two different contexts. Running them individually on your machine would work as it would be able to access those private endpoints.
Scheduling those to run in the Postman Cloud wouldn’t work as it wouldn’t be able to hit those private endpoints.
They would need to be publicly available for something like a Monitor to call them successfully.
1 Like