Sometimes request is giving EBUSY issue when hitting

[puneet0911]

I am using the request-promise to post and get a request from the API side and we are calling API using the interval to call the API in every 30 Seconds.
Sometime we will get the log like EBUSY.

Error: getaddrinfo EBUSY xxxx.xxxx.com\n    at new RequestError (/home/node_modules/request-promise-core/lib/errors.js:14:15)\n    at Request.plumbing.callback (/home/node_modules/request-promise-core/lib/plumbing.js:87:29)\n    at Request.RP$callback [as _callback] (/home/node_modules/request-promise-core/lib/plumbing.js:46:31)\n    at self.callback (/home/node_modules/request/request.js:185:22)\n    at Request.emit (events.js:203:13)\n    at
at Request.onRequestError (/home/node_modules/request/request.js:881:8)
    at ClientRequest.emit (events.js:203:13)
    at TLSSocket.socketErrorListener (_http_client.js:399:9)
    at TLSSocket.emit (events.js:203:13)
    at emitErrorNT (internal/streams/destroy.js:91:8)
    at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)
    at processTicksAndRejections (internal/process/task_queues.js:77:11)
(node:6571) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:6571) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Can anyone explain to me this? because it's not coming on every time.

We also used that try {} catch(e){} but its still breaking the interval.
Every time we have to execute it manually on the server after when its stops.