---
title: "Discussion on \"Why Cloudflare Pages Stopped Reading My _redirects at About 120 Rules\" | Hashnode"
description: "Discussion on \"Why Cloudflare Pages Stopped Reading My _redirects at About 120 Rules\". The docs allow 2,000 static and 100 dynamic redirects. My file gave out near rule 120. The limit is documented; the way rules are counted is easy to miss. Here is how to check your own file before deploy and after."
url: "https://hashnode.com/posts/why-cloudflare-pages-stopped-reading-my-redirects-at-about-120-rules/6ae072d2dcb798afd98261f1"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Why Cloudflare Pages Stopped Reading My \_redirects at About 120 Rules](https://katiabelokon.hashnode.dev/why-cloudflare-pages-stopped-reading-my-redirects-at-about-120-rules?utm_source=hashnode&utm_medium=feed)

The docs allow 2,000 static and 100 dynamic redirects. My file gave out near rule 120. The limit is documented; the way rules are counted is easy to miss. Here is how to check your own file before deploy and after.

Oct 27 · 10 min read · katiabelokon.hashnode.dev  
Read the article

-   [#cloudflare](https://hashnode.com/tag/cloudflare)
-   [#webdev](https://hashnode.com/tag/webdev)
-   [#devops](https://hashnode.com/tag/devops)
-   [#seo](https://hashnode.com/tag/seo)
-   [#javascript](https://hashnode.com/tag/javascript)

## Written by

[Katia Belokon](https://hashnode.com/@katiabelokon)

@katiabelokon · Los Angeles, USA

  
[View profile](https://hashnode.com/@katiabelokon)

Founder @ MyIPScan.net — DNS leaks, IP exposure & browser privacy checks

Founder of MyIPScan.net — a free network privacy toolkit: DNS/IPv6 leak tests, browser fingerprint check, IP exposure reports. We write practical guides on VPNs and home network security.

## Responses 4

Markdown supported · ⌘↵ to post

[Abhinav Sharma](https://hashnode.com/@abhinavs1920)

[Oct 27](https://hashnode.com/posts/why-cloudflare-pages-stopped-reading-my-redirects-at-about-120-rules/6ae072d2dcb798afd98261f1/comment/6ae09b0c897c9a6aa554f7d9)

The distinction between a matching explanation and a confirmed cause is helpful here. Have you tried the same small test file on a preview deploy to compare its cutoff with the local result?

[Katia Belokon](https://hashnode.com/@katiabelokon)

[Oct 28](https://hashnode.com/posts/why-cloudflare-pages-stopped-reading-my-redirects-at-about-120-rules/6ae072d2dcb798afd98261f1/comment/6ae09b0c897c9a6aa554f7d9#reply-6ae1f5abdef48565b2ec6cf0)

Thanks, Abhinav. No, I haven't, and that's the open gap in the post. The ~120 cutoff was on production, and the reproduction only ran locally in `wrangler pages dev`. So the post shows a mechanism that fits, not proof that production uses the same parser. A preview deploy of the same synthetic file would answer that, and if you or anyone else tries it, I'd be glad to hear the result.

[AI Developer](https://hashnode.com/@lycore)

[Oct 27](https://hashnode.com/posts/why-cloudflare-pages-stopped-reading-my-redirects-at-about-120-rules/6ae072d2dcb798afd98261f1/comment/6ae0784470a39067059607a6)

The positional classification detail is the interesting part: one early splat silently demotes every later rule into the 100-slot dynamic budget. A suggestion for the CI check: besides counting rules, also assert that every static rule precedes the first dynamic one, so reordering is enforced rather than remembered. A related question is whether a silent skip could be surfaced at build time, for example by diffing the parsed rule count against the line count in the deploy log. For the post-deploy curl check, it may also be worth asserting the Location header and status, since a rule that falls through to a catch-all 200 SPA fallback would not look like a 404 but would still be wrong.

[Katia Belokon](https://hashnode.com/@katiabelokon)

[Oct 28](https://hashnode.com/posts/why-cloudflare-pages-stopped-reading-my-redirects-at-about-120-rules/6ae072d2dcb798afd98261f1/comment/6ae0784470a39067059607a6#reply-6ae1f5f7baa25e6479cadeb9)

Thanks, both points are fair. The counting script already prints a WARN for every plain rule that comes after the first splat or placeholder, but it only warns. Adding `process.exit(1)` on that line would turn it into a failed build, which is what you describe. On the SPA fallback: the curl check compares both the status code and the Location header, so a 200 without a redirect shows up as a FAIL, not a pass.
