Feature flags: HTTP 403

Help Hub
, ,
1

When running collections from the Postman CLI I recently started to run into a not known error. I have been using the Postman CLI for some time now and this has not yet occurred. I use the following commands:

  • postman login –with-api-key {api-key}
  • postman collection run run {collection-id} -e {environment-id}

For some reason when running the collection I now get a ‘Feature flags: HTTP 403’ error and I have no clue why. Would anyone know anything about what could cause this error?

2

Hey @twoafas

Are you using the latest version of the CLI?

I’ve not seen that before but I can reach out to the team about that.

1 Like
3

Yes, I even did a fresh installation of Postman using NodeJS.

1 Like
5

I’m not sure what you mean by run in the cloud. The Postman CLI is on your machine it’s installed on. If you’re using the login command it will be auth’d against your user and it would be able to resolve the ids you’re passing in to the arguments.

Are you running this from the terminal or in a pipeline file?

Run this from the terminal will show which CLI version you are running:

postman -v
8

I’m not able to see anything that you have in front of you or know any commands that you’re using.

I’m more than happy to help but without over sharing the details, it’s a little one sided here. :folded_hands:

9

Ah, this was mistaken on my end. I was not completely aware on how the global variables worked. I have removed the messages on this issue to cause less clutter.

However the error message as described in my original post does still occur. I have also tested this with a personal account on a personal machine instead of my work environment and still the same message. Although not affecting my runs in any way it is still a strange bug.

10

Thanks for the heads-up on this — I verified it, corrected it, and kicked the tires with the CLI locally and in GitHub Actions. Should be smooth sailing from here out.

Cheers!

2 Likes