---
title: "Troubleshoot content delivery"
url: "https://developers.contentstack.com/paths/troubleshoot-content-delivery"
type: "path"
level: "intermediate"
outcome: "Delivery code that retries safely, stays within limits and returns the references and locales you expect."
steps:
  - "https://developers.contentstack.com/guides/etimedout-5xx-and-timeouts-from-the-delivery-api"
  - "https://developers.contentstack.com/guides/fix-429-rate-limit-errors-in-builds-imports-and-bulk-publish"
  - "https://developers.contentstack.com/guides/nested-references-empty-or-error-141"
  - "https://developers.contentstack.com/guides/why-am-i-getting-en-us-content-locale-fallback-explained"
  - "https://developers.contentstack.com/guides/graphql-errors-decoded"
  - "https://developers.contentstack.com/guides/contentstack-limits-on-one-page"
updated: "2026-11-15T11:47:30.955Z"
---

# Troubleshoot content delivery

- **Level:** Intermediate
- **Steps:** 6
- **Full path in one document:** https://developers.contentstack.com/paths/troubleshoot-content-delivery/full.md

---

Make Delivery API and GraphQL calls reliable. Handle timeouts and rate limits, fix empty references and unexpected locales, and know the limits before you hit them.

**You'll end up with:** Delivery code that retries safely, stays within limits and returns the references and locales you expect.

## Steps

1. [ETIMEDOUT, 5xx and timeouts from the Delivery API](https://developers.contentstack.com/guides/etimedout-5xx-and-timeouts-from-the-delivery-api) (Guide, Intermediate)
   - You'll end up with: Your builds and server-rendered pages survive slow responses, dropped connections and short 5xx spikes from the Delivery API, and you can tell a network problem from an API problem.
   - Checkpoint: Your fetch layer has timeouts, retries and keep-alive.
2. [Fix 429 rate limit errors in builds, imports and bulk publish](https://developers.contentstack.com/guides/fix-429-rate-limit-errors-in-builds-imports-and-bulk-publish) (Guide, Intermediate)
   - You'll end up with: You know which rate limit a 429 comes from, and your builds, imports, bulk publishes and scripts stay under it with backoff, pacing and fewer requests.
   - Checkpoint: Builds and imports back off instead of failing on 429.
3. [Nested references come back empty, or fail with error 141](https://developers.contentstack.com/guides/nested-references-empty-or-error-141) (Guide, Intermediate)
   - You'll end up with: You can tell why a reference comes back unresolved, empty or as a 422 error, fix the include paths, publish state or depth that caused it, and model new content so it stays inside the limits.
   - Checkpoint: Deep references resolve or are modeled around the depth limit.
4. [Why am I getting en-us content? Locale fallback explained](https://developers.contentstack.com/guides/why-am-i-getting-en-us-content-locale-fallback-explained) (Guide, Intermediate)
   - You'll end up with: You can tell why a request for one locale returns content from another, read the response to find out which case you are in, and fix it in the stack or in your query.
   - Checkpoint: Locale fallback behaves the way you configured it.
5. [GraphQL errors decoded: depth, cost and partial data](https://developers.contentstack.com/guides/graphql-errors-decoded) (Guide, Intermediate)
   - You'll end up with: You can read a Contentstack GraphQL error, tell a rejected query from a partial result, and rewrite queries so they stay inside the depth, cost and page size limits.
   - Checkpoint: You can read and fix GraphQL limit and partial-data errors.
6. [Contentstack limits on one page](https://developers.contentstack.com/guides/contentstack-limits-on-one-page) (Guide, Beginner)
   - You'll end up with: You know the public Contentstack limits that affect your content model, your queries and your jobs, which of them depend on your plan, and what happens when you hit one.
   - Checkpoint: You know the limits that apply to your plan and code.

