Error 1200 indicates requests queued at Cloudflare’s edge while awaiting the origin. Compare the failure time with host capacity and the requests that actually need to reach WordPress.
Origin tuning and suitable caching can reduce this work. Keep personalized pages out of shared cache and avoid repeated broad purges that remove useful cached responses.
Guide reviewed: October 8, 2026. Interface labels may vary by version, account and device.
Confirm where the origin queue forms
| Evidence | Inspect | Next investigation |
|---|---|---|
| Surge at the failure time | Traffic and origin capacity | Queue under peak demand |
| Normal traffic, persistent delays | Slow application path | Queries, workers or dependencies |
| Static resources bypass cache | Actual cache status and rules | Intended cache behavior |
| Dynamic account or cart page | Personalized response requirements | Preserve correct user data |
| Rapid retries or broad purges | Client behavior and cache changes | Avoid adding work during the incident |
Connect the error with the traffic at that time
- Record URL, message and time zone.
- Compare traffic and host resource information for that period.
- Identify whether the affected requests are cached or dynamic.
- Ask the host where incoming work waits.
- Evaluate the identified bottleneck before choosing an unspecified upgrade.
Record when the message appeared and compare it with the host’s resource and connection information for the same period. A brief traffic surge and a persistently slow origin can create different patterns, even though both may leave requests waiting.
For example, a campaign might send many readers to an uncached page at once. If the host cannot process those requests quickly enough, a queue can grow. Another site might encounter the problem during ordinary traffic because the underlying request path is already slow.
The error alone does not decide which situation applies. The host’s logs, the affected URLs and the traffic pattern give the administrator a better basis for a correction.
Find which requests actually reach the origin
Keep a small sample of public static, public content and personalized requests with their observed cache behavior. A single miss is not proof of a fault; repeated behavior needs comparison with the intended rules and content.
Cloudflare can serve eligible cached content without making a new origin request for each visit. Content that is not cached follows the longer path to the hosting server. Reviewing cache behavior therefore helps explain the volume of work reaching WordPress.
Start with public static resources and the pages affected by the error. A developer can inspect the cache status and compare it with the intended rules. An unexpected bypass on a static asset is a different issue from a deliberately dynamic account page.
A cache miss on one request is not automatically a faulty configuration. The useful question is whether the repeated behavior fits the content and its rules. Cache analytics can help identify patterns rather than relying on one isolated response.
Keep private content out of shared cache
Improving the cache-hit rate does not mean caching every WordPress response. Account pages, shopping carts and other personalized content need a design that preserves the correct information for each user.
A public article and a signed-in dashboard should not be given the same broad caching treatment merely to reduce origin traffic. The administrator should know which responses are safe to share and which require an individual result.
Test signed-in and signed-out behavior after a caching change. A faster response that shows one person’s information to another is not an acceptable performance improvement.
Ask the host about the origin bottleneck
Cloudflare’s guidance recommends tuning the origin to accept incoming connections faster. The hosting provider can help identify what is limiting that work, such as the available processing capacity or a slow application request.
Provide the time, affected URL and complete error rather than asking for an unspecified upgrade. The host can compare those details with its records and explain whether the issue is capacity, configuration or a particular workload.
If the slow path is a specific WordPress feature, its developer may need to review the underlying queries or processing. Increasing capacity can help some workloads, but it should not replace an investigation of work that is unnecessarily repeated.
Avoid actions that increase the queue
Rapid retries create more work when the origin is already struggling. Automated clients should respect applicable retry guidance. Cloudflare lists a Retry-After value of 60 seconds for this code, but the underlying bottleneck still needs attention if the symptom returns.
Repeated broad cache purges can also remove useful cached responses at the moment they are most helpful. A purge should have a specific purpose, such as removing stale content, rather than being the default response to every connection error.
After the identified correction, repeat the affected request and compare cache behavior and origin response performance. Then check the important dynamic workflows that must continue reaching the application. The result should show both recovery and correct content.
Cloudflare’s error 1200 guide explains the queue and origin tuning. Its slow website troubleshooting guide covers cache investigation and the care needed with personalized responses.
Verify performance and correct content
Retest the affected request and compare origin response performance and cache behavior. Check signed-in and signed-out workflows separately. Confirm that personalized pages show the correct user’s result after any caching change.