---
title: "Comment by AI Developer on \"Why Cloudflare Pages Stopped Reading My _redirects at About 120 Rules\" | Hashnode"
description: "The positional classification detail is the interesting part: one early splat silently demotes every later rule into the 100-slot dynamic budget. A suggestion f"
url: "https://hashnode.com/posts/why-cloudflare-pages-stopped-reading-my-redirects-at-about-120-rules/6ae072d2dcb798afd98261f1/comment/6ae0784470a39067059607a6"
---

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

Comment [Why Cloudflare Pages Stopped Reading My \_redirects at About 120 Rules](https://hashnode.com/posts/why-cloudflare-pages-stopped-reading-my-redirects-at-about-120-rules/6ae072d2dcb798afd98261f1)

[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.
