Monitor Collection- I ran Monitor collection manually couple of times and is 100% failed where the same collection works fine when ran through Postman/Newman

tmccann · June 8, 2018, 3:34pm

My guess here would be that there is a bit of a domino effect happening. The first call failure causes the other errors you are seeing in the console.

I believe the issue would be that you are running the Monitor that can only connect to publicly available resources and the end point you are trying to reach Error: connect ETIMEDOUT 192.168.20.220:6002 is not externally accessible?

Topic		Replies	Views
Collection test pass but Monitor Fails? Ask the Experts and Postman Tips monitors , collections	0	431	May 9, 2023
Response code fails only when test runs in browser's monitor Ask the Experts and Postman Tips monitors , tests , authentication , json	10	2788	June 16, 2023
Monitoring Authorization Error Ask the Experts and Postman Tips	2	2016	January 4, 2021
Monitor doesn't recognize api keys Ask the Experts and Postman Tips monitors , collections , authentication	8	1786	January 15, 2021
Monitor calls failing Ask the Experts and Postman Tips monitors , collections	2	22	November 1, 2024

Monitor Collection- I ran Monitor collection manually couple of times and is 100% failed where the same collection works fine when ran through Postman/Newman

Related topics