Your site talks to Contentful through its API, so a Contentful problem shows up as a failed API request. Check Contentful's status page for incidents, then read the status code your site got back. 401: the access token is wrong, expired or revoked. 404: the space, environment or entry ID doesn't exist (often the wrong environment). 429: too many requests, so slow down and cache. 5xx: a problem on Contentful's side.
What's the problem
Your site shows missing content, a build fails while fetching content, or API calls to Contentful return errors.
Why it happens
- A wrong or revoked access token.
- The wrong space or environment ID in your site's settings.
- Content not published, so the delivery API doesn't return it.
- Rate limits from builds or pages that fetch too much at once.
- Content model changes (renamed fields) that your code still expects.
- A Contentful incident.
How to fix it
- Check Contentful's status page.
- Read the status code and message from the failed request in your logs or build output.
- Check the token, space ID and environment your live site uses.
- Check the content is published.
- For 429s, cache responses and reduce how many requests your build or pages make.
- If fields were renamed, update your code to match the content model.
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
- Contentful: Contentful Statusstatus page
Get email notifications whenever Contentful creates , updates or resolves an incident.
- MDN Web Docs: 401 Unauthorizedreference
The HTTP 401 Unauthorized client error response status code indicates that a request was not successful because it lacks valid authentication credentials for the requested resource.
- MDN Web Docs: 429 Too Many Requestsreference
The HTTP 429 Too Many Requests client error response status code indicates the client has sent too many requests in a given amount of time.
Preventionlabs is independent and not affiliated with Contentful. Product names are used only to describe the problem.
← All of Headless CMS