Hi everyone,
A few days ago we noticed an issue where some fields return values from the API/GraphQL that don’t match what’s currently set in Prismic.
For example:
-
We have a select field “button label” with options
"ComingSoon","BuyNow","LearnMore". -
In Prismic, the value is set to
"BuyNow". -
But when fetching data, the API/GraphQL response returns
"ComingSoon".
Looking at the history, on May 15, 2024 at 10:30AM, the field was changed from "ComingSoon" to "BuyNow". This change was attributed to a user who no longer exists in Prismic (it shows as “Last Published by Ghost”).
We’ve also observed similar mismatches in other fields, where the API returns values that don’t reflect what’s currently in the Prismic UI.
Concerns
-
We have over 50,000 documents, so there might be more affected documents we can’t easily detect.
-
We don’t understand how this happened, which means we also can’t create any internal guidelines to prevent it — if it was even on our side to begin with.
Additional Notes
-
The issue appears in both GraphQL and REST API.
-
Once the document is saved again, the API returns the correct value.
What we’re asking
We’d appreciate it if you could:
-
Assess and confirm whether this is a known issue or something unique.
-
Suggest how we can analyze/filter our documents to detect others that might be affected.
-
Recommend preventive measures (if this could have been caused by a workflow mistake on our side).
Disclaimer
We need to set the correct values for the known documents, we are concerned that in that case your team might loose a test case. We’d appreciate your opinion.
Thanks in advance for any insights or guidance!
We are available to provide you with additional info you might need.
