# Monitors JSONError: Unexpected token u in JSON at position 0 **URL:** \ **Category:** Help Hub\ **Tags:** monitors, collections, response\ **Created:** [December 1, 2020, 9:29pm UTC](https://community.postman.com/t/monitors-jsonerror-unexpected-token-u-in-json-at-position-0/18155 "2020-12-01T21:29:52Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![Chandana](https://avatars.discourse-cdn.com/v4/letter/c/b5a626/32.png) [@Chandana](https://community.postman.com/u/Chandana)\ **Post date:** [December 1, 2020, 9:29pm UTC](https://community.postman.com/t/monitors-jsonerror-unexpected-token-u-in-json-at-position-0/18155/1 "2020-12-01T21:29:52Z")
Getting this error twice in the monitor. What would initiate this error? ---
**Author:** ![allenheltondev](https://sea2.discourse-cdn.com/getpostman/user_avatar/community.postman.com/allenheltondev/32/31738_2.png) [@allenheltondev](https://community.postman.com/u/allenheltondev)\ **Post date:** [December 3, 2020, 12:42pm UTC](https://community.postman.com/t/monitors-jsonerror-unexpected-token-u-in-json-at-position-0/18155/2 "2020-12-03T12:42:11Z")
You get that error when the response returned from your API is invalid JSON. Do you get this every time the monitor runs or has this only happened twice ever? If it doesn’t happen every time the monitor runs, it makes me think the problem does not lie with the monitor itself. ---
**Author:** ![Chandana](https://avatars.discourse-cdn.com/v4/letter/c/b5a626/32.png) [@Chandana](https://community.postman.com/u/Chandana)\ **Post date:** [December 3, 2020, 3:29pm UTC](https://community.postman.com/t/monitors-jsonerror-unexpected-token-u-in-json-at-position-0/18155/3 "2020-12-03T15:29:29Z")
Allen, This happens every single time I run the monitor. I do not get any errors in postman app, I only see this error in monitor. ![image](https://us1.discourse-cdn.com/getpostman/original/3X/1/0/102c8cc68bc64c2d085c8128d2bfc53060f2a2a6.png) ---
**Author:** ![allenheltondev](https://sea2.discourse-cdn.com/getpostman/user_avatar/community.postman.com/allenheltondev/32/31738_2.png) [@allenheltondev](https://community.postman.com/u/allenheltondev)\ **Post date:** [December 4, 2020, 12:27pm UTC](https://community.postman.com/t/monitors-jsonerror-unexpected-token-u-in-json-at-position-0/18155/4 "2020-12-04T12:27:22Z")
Are you running it in the same environment as you are locally? Does your request require some Auth that might not be getting set? ---
**Author:** ![Chandana](https://avatars.discourse-cdn.com/v4/letter/c/b5a626/32.png) [@Chandana](https://community.postman.com/u/Chandana)\ **Post date:** [December 4, 2020, 5:56pm UTC](https://community.postman.com/t/monitors-jsonerror-unexpected-token-u-in-json-at-position-0/18155/5 "2020-12-04T17:56:21Z")
Are you running it in the same environment as you are locally? Yes Does your request require some Auth that might not be getting set? No ---
**Author:** ![vkuppena](https://avatars.discourse-cdn.com/v4/letter/v/8dc957/32.png) [@vkuppena](https://community.postman.com/u/vkuppena)\ **Post date:** [February 4, 2022, 4:50pm UTC](https://community.postman.com/t/monitors-jsonerror-unexpected-token-u-in-json-at-position-0/18155/6 "2022-02-04T16:50:23Z")
Was there any resolution on this? I am facing exact same issue… The sequence of API requests work fine on running th collection but get the JSONError: Unexpected token u in JSON at position 0 on running the same collection in Monitor. ---
**Author:** ![prodwest](https://avatars.discourse-cdn.com/v4/letter/p/e95f7d/32.png) [@prodwest](https://community.postman.com/u/prodwest)\ **Post date:** [June 30, 2022, 10:50pm UTC](https://community.postman.com/t/monitors-jsonerror-unexpected-token-u-in-json-at-position-0/18155/7 "2022-06-30T22:50:07Z")
Hi Team, do we any solution for this issue? I’m facing this issue intermittently and couldn’t find the reason. Any one who already faced and fixed, pls help me. Thanks in advance! Ram ---
**Author:** ![itsram112](https://avatars.discourse-cdn.com/v4/letter/i/e19b73/32.png) [@itsram112](https://community.postman.com/u/itsram112)\ **Post date:** [July 5, 2022, 2:36pm UTC](https://community.postman.com/t/monitors-jsonerror-unexpected-token-u-in-json-at-position-0/18155/8 "2022-07-05T14:36:20Z")
additional info, when getting this error, there is no **StatusCode** and **Response Body**. **Unexpected token u in JSON at position 0** ---
**Author:** ![rapidkieron](https://avatars.discourse-cdn.com/v4/letter/r/3bc359/32.png) [@rapidkieron](https://community.postman.com/u/rapidkieron)\ **Post date:** [December 19, 2023, 5:41am UTC](https://community.postman.com/t/monitors-jsonerror-unexpected-token-u-in-json-at-position-0/18155/9 "2023-12-19T05:41:27Z")
Having precisely the same issue: I am running a monitor on a collection which runs a pre-request script to get a authentication token. When I send the POST request manually it succeeds. When I run the Monitor or a Scheduled Run I get this error: Error:‌ connect ETIMEDOUT xx.‌xxx.‌xxx.‌xxx:‌xxx JSONError:‌ Unexpected token u in JSON at position 0 All are performed within the same Environment. Is there any more information I can provide to help solve this? Did any of the other posters resolve this? ---
**Author:** ![michaelderekjones](https://sea2.discourse-cdn.com/getpostman/user_avatar/community.postman.com/michaelderekjones/32/14819_2.png) [@michaelderekjones](https://community.postman.com/u/michaelderekjones)\ **Post date:** [December 19, 2023, 12:25pm UTC](https://community.postman.com/t/monitors-jsonerror-unexpected-token-u-in-json-at-position-0/18155/10 "2023-12-19T12:25:25Z")
@rapidkieron Monitors and scheduled jobs are run from the Postman Cloud. My first question would be whether you can access the token end point from the Internet. ---
**Author:** ![rapidkieron](https://avatars.discourse-cdn.com/v4/letter/r/3bc359/32.png) [@rapidkieron](https://community.postman.com/u/rapidkieron)\ **Post date:** [December 21, 2023, 5:06am UTC](https://community.postman.com/t/monitors-jsonerror-unexpected-token-u-in-json-at-position-0/18155/11 "2023-12-21T05:06:26Z")
Thanks Mike. Had not realised the Monitors run from the cloud. Believe that is the issue.