# Running monitor reports serverError when monitor completes fine

**URL:** <https://community.postman.com/t/running-monitor-reports-servererror-when-monitor-completes-fine/22920>\
**Category:** Help Hub\
**Tags:** monitors, curl\
**Created:** [April 20, 2021, 8:31pm UTC](https://community.postman.com/t/running-monitor-reports-servererror-when-monitor-completes-fine/22920 "2021-04-20T20:31:01Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![briffle](https://avatars.discourse-cdn.com/v4/letter/b/c68b51/32.png) [@briffle](https://community.postman.com/u/briffle)\
**Post date:** [April 20, 2021, 8:31pm UTC](https://community.postman.com/t/running-monitor-reports-servererror-when-monitor-completes-fine/22920/1 "2021-04-20T20:31:01Z")

</div>

_My question_: I am calling a postman monitor as part of our deployment process for testing. I use curl to call the monitor with:  
`curl --max-time 900 -X POST -H "X-API-KEY:${POSTMAN_KEY}" https://api.getpostman.com/monitors/${POSTMAN_MONITOR}/run/ | jq '.'`

This works for kicking off the monitor. However, I regularly (but not always) get back a response of:  
{  
“error”: {  
“name”: “serverError”,  
“message”: “Something went wrong with the server.”  
}  
}

When I log into postman and look, the entire monitor ran without any errors in about 110 seconds.

_Details (like screenshots)_:

 ![image](https://us1.discourse-cdn.com/getpostman/original/2X/7/7a2202118c351a84bd1c65bd2811d2489bb43f98.png)

_I’ve already tried_: Adding timeouts to curl.