***

title: I am having trouble running my monitor
description: >-
You are experiencing the following issue You're seeing failures in your
Monitor Summary , although all your tests have passed: Error: callback timed
out Erro...
-----------

## You are experiencing the following issue

You're seeing failures in your [Monitor Summary](/docs/monitoring-your-api/viewing-monitor-results/#monitor-summary), although all your tests have passed:

* *Error: callback timed out*
* *Error: NETERR: getaddrinfo ENOTFOUND*
* *Error: getaddrinfo ENOTFOUND*
* *Error: ESOCKETTIMEDOUT*
* *TypeError: Cannot read property'objectID' of undefined / Cannot read property'has' of undefined*
* *You cannot run monitors right now. Check your usage for details.*

## How to unblock yourself

**Important:** Verify your monitor's [Console Log](/docs/monitoring-your-api/viewing-monitor-results/#console-log) to view the error and the exact reason for the failed run.

### Error: callback timed out

Monitor runs are subject to a 10-minute timeout. This error is thrown when the timeout is breached.

* Use the Collection Runner to verify how long the collection run takes to [execute.](/docs/collections/running-collections/intro-to-collection-runs/) If it takes less than 10 minutes, try running the monitor from the [closest region selected,](/docs/monitoring-your-api/intro-monitors/#multi-region-monitoring) which might result in shorter response times.

### Error: NETERR: getaddrinfo ENOTFOUND

The error happens when the variables aren't resolved for a particular request while running your collection through the monitor.

* Verify if you have global variables in use for the collection. If so, using environment variables instead of globals should fix this error.

### Error: getaddrinfo ENOTFOUND

This error usually implies a DNS error.

* Verify your proxy configuration.
  * If you're using an older version of the application, update to the latest version.

### Error: ESOCKETTIMEDOUT

The issue might be due to any network element that the requests hop through between the API server and the Monitoring server, which can increase network latency.

* Check if any changes to the network elements (Load balancers, Firewalls, etc) might be behind this issue.

### TypeError: Cannot read property'objectID' of undefined / Cannot read property'has' of undefined

Monitors require all URLs to be publicly available on the internet as they run in the Postman Cloud. A monitor cannot directly access your local host or run requests behind a firewall.

* Verify if the endpoints you're trying to hit are hosted publicly.

### You cannot run monitors right now. Check your usage for details.

This happens when your team's monthly plan for monitors is exceeded.

* You can view your team's monitoring usage [here](https://go.postman.co/billing/add-ons/overview) and purchase Add-ons from the same page.

***

Have more questions? [Submit a request](/help/submit-request)

***