I have an API first schema definition using OpenAPI.
I generated a collection for “documentation” from that schema.
When I go to the develop tab and click “validate” I get errors.
When I try to “select all” and fix those errors, they do not go away.
If this is “generated” why are there errors?
Why doesn’t the validation confirmation changes fix the problems.
I can only add three images, so skipping the first one where I click on “select all” and “confirm”
Yes, if I “validate again”. I see the same errors as before.
I didn’t upload the first image (due to 3 image limit), but it looked the same as the last image
Got it thanks, let me see if I can get some input on this.
Hey @enric.ribas , is it possible to share the schema? It will help us in triaging the issue. 
@enric.ribas Since I do not have the access to the workspace, could you upload the schema file in the comment or email at help@getpostman.com?
Hey @enric.ribas, Thanks for sharing the schema. The schema that we received had syntax errors(invalid JSON). We fixed the errors and tried the steps mentioned here. We could not reproduce it. Could you check if you are still seeing any errors? If yes, would it be possible to send a video recording of the steps to reproduce it?
I don’t know how it had errors since I did an export of schema from Postman, which does not show me any errors. 
First image, removed a comma to prove that an error in schema will prevent “prettify”. Schema has unsaved changes.
Second image, added back the removed comma, no unsaved changes. There are no errors, I can run prettify with no issues. I export the schema, copy to VSCode, save as JSON.
FYI:
It says the schema is validated at the bottom, so not what errors you are seeing. Not sure what else I can do.
Can you not check if my schema is valid without copy/pasting ? Can you check the status of my API?
Here is a link to a video where you can see my schema is Valid.
I try to validate issues. It says they are validated, but then the issues are back again.
https://drive.google.com/file/d/1HX56dYmZ7kmX43VtTCNfuX8_aI14TIrU/view?usp=sharing
Hey @enric.ribas, thanks for sharing the video. We are able to reproduce the issue now. We are working on the fix and will update here once this is resolved.
