Sometimes, even the best systems hit a snag. If you’ve run into a timeout or 5xx server error while using Enrich Layer’s APIs, don’t worry — this guide walks you through what’s likely happening and what to do next.
💥 What’s a Timeout or 5xx Error?
These errors usually mean your request couldn’t be completed due to temporary issues — either on your side, Enrich Layer’s servers, or in rare cases, the upstream data sources.
Common Scenarios:
Timeout (Request Timed Out) The server took too long to respond. This can happen if the payload is large, the endpoint is under high load, or the response relies on a slower upstream source.
500 Internal Server Error A general server issue. It’s not your fault, and it’s usually temporary.
502 / 503 / 504 Errors These often relate to infrastructure hiccups — maintenance, upstream delays, or brief outages.
🔁 When Should You Retry?
Most of these errors resolve quickly. Here’s how to handle them:
Timeouts (no response): Retry after a short delay (e.g., 10–30 seconds). If it persists, try reducing the request size or complexity (e.g., using fewer enrichments or a smaller page_size).
5xx errors: Retry with exponential backoff — meaning wait a bit longer between each retry (e.g., 10s → 30s → 60s). This helps prevents server overload and improves your chances of a successful response.
⚠️ Repeated 5xx errors?
Reach out to support — we’ll investigate and help you troubleshoot.
🛠 Pro Tips for Stability
Use page_size thoughtfully: Large batch requests are more likely to time out. Start smaller and scale up.
Avoid back-to-back large requests: Add pause or spacing between high-volume API calls.
Keep an eye on your retry logic: Make sure it includes a limit and alert system to help catch persistent failures without needing custom scripts.
Still Stuck?
If you’re consistently seeing timeouts or 5xx errors, send us a message via live chat using the bubble in the bottom-right corner. We’ll help identify the issue and guide you toward a fix.