Repeatable group lost all but one item

Developing with Prismic
,
1

Describe your question/issue in detail

We are experiencing unexpected data loss in one of our repeatable groups within a custom type. Out of nowhere, all items in the group disappeared except one. What’s strange is that when we checked the document history of affected pages, there is no record of those missing items ever being added, even though they were previously visible and in use on the live site.

No content changes were pushed recently, and we haven’t modified the custom type via Slice Machine in a while. This incident occurred without any manual intervention.

We’re concerned there might be a bug or syncing issue between the Prismic CMS and Slice Machine.

Impacted feature

Repeatable Group field inside a Custom Type (specifically a group of items in a slice shared across multiple pages). The data appears to have been deleted or rolled back silently.

What steps have you taken to resolve this issue already?

  • Verified no changes were pushed via Slice Machine
  • Checked the document history of affected pages (no record of the missing items)
  • Refreshed and checked the API responses from Prismic
  • Reviewed recent deployment and content logs
  • Searched project repository for recent schema changes (none found)
  • Ensured the issue wasn’t related to preview or caching

Errors

There are no visible errors in the CMS or in our build/deploy logs. The missing data simply disappeared.

Your Role

Tech Lead

Hosting provider

N/A

Package.json file

N/A
``

Steps to reproduce

Unfortunately, this issue occurred without a clear trigger. However:

  1. We created a repeatable group inside a slice.
  2. Editors populated several items in the group via the Prismic CMS UI.
  3. These items were visible on the live site.
  4. At some point, all items disappeared except one.
  5. No change in document history reflects when they were added or removed.
  6. No code or schema changes were pushed around this time.
2

Hi Manuel,

Thanks for the context and welcome to the community.

This isn't something we've been able to reproduce either, which makes it trickier to pinpoint. One possibility that comes to mind is if the group items were added during a preview session, but never actually saved + published. In that case, the content would’ve been visible on the site temporarily, but wouldn't be saved in the document history or show up in the API later on.

If your team uses Prismic’s preview functionality, that might the cause behind it. Without a way to reproduce it makes it hard to debug if it was something else. If you notice the issue again, we’d love to dig deeper with more details.