Documentation - Content missing after Postman upgrades

[liam-sarson]

Hi All,

we have experienced a problem recently with our first partner site publication.
We have compiled a GraphQL collection for some of our development partners. We use introspection and ensure our schema is well documented.

But the thing is we have been using the API documentation to provide some context to our partners as to the order or use, the logic that sits behind our APIs and giving developers who are used to REST a bit of a background as to how GraphQL works and how our services all come together.

its a bit of hand holding that makes our lives easier. However we had been using collection folders to provide some of this context. However recently we have noticed since recent updates to postman, this content has been removed / restricted. its like there is a character limit (which doesnt seem to be enforced when the content is created) but recent cloud updates seem to of removed this content.

Its frustrating as we are not able to recover this content and have no ability to find any audit logs of the initial documentation.

Has anybody else experienced this or have any suggestions about how to potentially recover.

I can’t trust postman at the moment with this, so may need to look at alternative methods but for now, I just want to try and recover what was published.

Is this a bug that is known or is it a known limitation of the documentation.

Thanks in Advance

[danny-dainton]

Hey @liam-sarson

Welcome to the Postman Community!

Apologies for not getting to this quicker - Do you have any visual examples of the place where you see thing being removed of restricted?

It will help the team to investigate the issue further

There are changelogs on the Collections and depending on the plan type you will be able to see a detailed look at which changes have been made.

Manage and organize Postman Collections | Postman Docs

I’ve not seen any other reports on the same issues coming from users but I will take a another look around to different incoming feedback resources again.

[spacecraft-pilot-270 (Juris)]

Hello @danny-dainton,

I’m experiencing the same thing - the graphql folder documentation behaves as if there is a hard limit of 2048 characters. As soon as the tab (or postman app) is reloaded, the truncates everything after 2048th character.

Here are some screenshots of reproduction steps:

1. Create a new workspace and select new graphql request

2. Save the request to a new collection

3. Create documentation/overview for the collection that exceeds 2048 characters

4. Save the collection

5. Reload the tab and observe that the content is truncated

There are changelogs on the Collections and depending on the plan type you will be able to see a detailed look at which changes have been made.

I don’t see this feature anywhere for gql collections, there’s no way to get edit history to get back the deleted content.

Hope this helps with identifying the source of the issue

(FYI - this wasn’t always the case, seems to have started sometime in August if I recall correctly)

[spacecraft-pilot-270 (Juris)]

Hello @danny-dainton ,

are there any updates on this? The issue seems quite important since it implies user data loss and is preventing us from using the collection documentation feature.

[danny-dainton]

I’ve informed the team about this and hopefully I’ll be able to post an update soon.

Have you created a new issue on our Github Tracker for this problem? It’s the best place to raised product issues and get them in front of the development team.

Build software better, together