Response code fails only when test runs in browser's monitor

[taehoshino]

Hi @billybolton! Welcome to the community

I understand your tests fail only when you run the collection with Postman Monitor, is that correct?

As Postman Monitor is being executed on the Postman server, there are a few differences to be noted, compared to when you run collections locally - please refer to the thread below for more information.

Monitoring Authorization Error

Hi @jbalasi! I understand you are using a API key that is set as a global variable when running a monitor, correct? Monitor does not have access to global variables so use collection/environment variables instead. FYI, a few differences between runner and monitor: All API must be publicly available No access to global variables (use collection/environment variables instead) No access to CURRENT VALUE (remember CURRENT VALUE is local to your session) Hope this helps!

Having said that, in your current situation, I wonder if your api keys are stored in CURRENT VALUES of environment - if so, please copy them to INITIAL VALUES so that those values are accessible by the Monitor.

You also mentioned you would like to check the value used for api keys - for this, you can simply include console.log() in Test scripts. This will then printed out in the console log tab of your Monitor page.

Hope this helps! Please let me know if you have further questions