Open abrunke opened 1 year ago
It's worth noting that when I export the collection from the Postman Desktop app the JSON is as expected.
When the GitHub integration to back up the collection triggers however the collection it's backing up is NOT as expected
It also seems that when the collection is duplicated that the JSON returned is as expected. So there's something a miss with 11955658-f6d4ed04-6dfc-4763-9a54-cb9bb5085376
specifically.
Since this is our main collection that all automated tests run from we have various open forks. So switching to a new duplicate is a little more involved.
Is there an existing issue for this?
Describe the Issue
When using the https://api.getpostman.com/collections/ endpoint to return a collection the json returned doesn't match the collection.
This is impacting the ability to run Newman & Postman CLI as the folder isn't found and thus 0 iterations execute.
However if I fork the collection and run from the fork the json is as expected.
Running the folder from the collection in the manual runner in the postman app works without issue. So this seems isolated to what's being returned in https://api.getpostman.com/collections/ not being in sync with what's actually in the collection
Steps To Reproduce
"name": "checkoutApi-getPaymentMethods"
"name": "checkoutApi-getPaymentMethods"
is in the JSONScreenshots or Videos
Desktop App
JSON from: https://api.getpostman.com/collections/11955658-f6d4ed04-6dfc-4763-9a54-cb9bb5085376
JSON from: https://api.getpostman.com/collections/10822386-a91e4348-03fc-45e8-b19b-b1274ea18314
Operating System
Window
Postman Version
10.12.13
Postman Platform
Postman App
User Account Type
Signed In User
Additional Context?
No response