Hello, I have a “run in postman” button in some public documentation, normally users can copy the collection this way however periodically they get an error. Randomly it will start working again but we keep getting reports from users who are unable to copy it.
I did manage to capture it failing but the http response was a generic 403. It started working again a few minutes after I noticed it failing.
I’ve passed the details onto the team to take a look at and see what’s happening here. I will come back here and update the thread with any information I receive.
If the issue persists, please raise this as an issue on our public issue tracker:
The user seems to be trying to import a private collection that they don’t have access to. Hence the 403. Only the user with view access can import this collection and in this case, it’s in a personal workspace
We’re also improving the error message seen in the UI to give more contextual information about the issue.
It’s strange because previously it’s gone from not working to working again, which implies it should be sat in a public workspace, however I’m struggling to pin down whose account it’s attached to annoyingly. I can try reshare it on my account and see if that fixes it.
Just so I’m not missing anything, can I confirm that collections that:
Exist in a public workspace
On an unpaid account
And being shared though the app.getpostman.com/run-collection/<collection_id> endpoint
Shouldn’t have any issues with it occasionally not working, e.g. the link timing out or failing due to too many people trying to use it
