Prismic's Content API needs an access token to read private repositories, so a missing, wrong or revoked token is the first thing to check if content stopped loading. After that, check the repository name in your site's settings, that the document is published, and the status code of the failed request in your logs or build output.
What's the problem
Your site shows missing content, pages 404, a build fails fetching content, or Prismic API calls return errors.
Why it happens
- A missing or wrong access token for a private repository.
- The wrong repository name in your settings.
- Unpublished documents, or a changed document ID or UID.
- Custom type or slice changes your code doesn't handle yet.
- Build-time caching serving old content.
How to fix it
- Read the failed request's status and message.
- Check the access token in your live environment if the repository is private.
- Check the repository name.
- Check the document is published and its UID matches the link.
- Update your code for changed custom types or slices.
- Rebuild or clear caches after publishing.
What Preventionlabs checks
One click runs the full report on your domain. For this problem it shows whether your site loads, how fast, and where its redirects go; up to 50 pages from your sitemap, listing any that fail or are slow, plus broken links on them. With Cloudflare connected, it also shows recent deploys and account changes, with their times. It has no connection to your CMS itself, so check the CMS's status page and API settings too.
Run your free reportYour first report is free, no card needed. Then A$50 a month, up to 10 domains. Read-only: it never changes anything.
Sources
Preventionlabs is independent and not affiliated with Prismic. Product names are used only to describe the problem.
← All of Headless CMS