nextjs - 💡(How to fix) Fix Docs: Fix broken link in ci-build-caching [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
vercel/next.js#92601Fetched 2026-04-11 06:08:16
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Author
Participants
Assignees
Timeline (top)
assigned ×1closed ×1commented ×1issue_type_added ×1

Error Message

On https://nextjs.org/docs/15/app/guides/ci-build-caching, there is a link to the "No Cache Detected" error page. Clicking it returns a 404 error because the href is set to /docs/15/messages/no-cache, but that path does not exist. "you may see a No Cache Detected error."

Root Cause

On https://nextjs.org/docs/15/app/guides/ci-build-caching, there is a link to the "No Cache Detected" error page. Clicking it returns a 404 error because the href is set to /docs/15/messages/no-cache, but that path does not exist.

RAW_BUFFERClick to expand / collapse

What is the documentation issue?

The "No Cache Detected" link in the v15 CI Build Caching docs page is broken.

<img width="530" height="143" alt="Image" src="https://github.com/user-attachments/assets/42087cbd-b787-4d5f-a9c7-9743bd80a867" />

On https://nextjs.org/docs/15/app/guides/ci-build-caching, there is a link to the "No Cache Detected" error page. Clicking it returns a 404 error because the href is set to /docs/15/messages/no-cache, but that path does not exist.

Is there any context that might help us understand?

The broken link appears in this sentence at the top of the page: "you may see a No Cache Detected error."

The current href resolves to: https://nextjs.org/docs/15/messages/no-cache (404)

The canary version of the same page uses /docs/messages/no-cache, which works correctly: https://nextjs.org/docs/messages/no-cache

The fix would be to either:

  1. Change the link href to /docs/messages/no-cache (without the version prefix), or
  2. Create the appropriate redirect for /docs/15/messages/no-cache

Does the docs page already exist? Please link to it.

https://nextjs.org/docs/15/app/guides/ci-build-caching

extent analysis

TL;DR

Update the "No Cache Detected" link in the v15 CI Build Caching docs page to point to /docs/messages/no-cache to fix the 404 error.

Guidance

  • Verify the issue by checking the link on the CI Build Caching docs page and confirm it returns a 404 error.
  • Update the link href to /docs/messages/no-cache (without the version prefix) as a direct fix.
  • Alternatively, consider creating a redirect for /docs/15/messages/no-cache to maintain version-specific URLs.
  • Test the updated link to ensure it resolves correctly and no longer returns a 404 error.

Example

No code snippet is necessary for this fix, as it involves updating a documentation link.

Notes

This fix assumes that the /docs/messages/no-cache page is the intended target for the "No Cache Detected" link and that removing the version prefix is acceptable.

Recommendation

Apply the workaround by updating the link href to /docs/messages/no-cache, as it is a straightforward fix that resolves the 404 error without requiring additional infrastructure changes.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

nextjs - 💡(How to fix) Fix Docs: Fix broken link in ci-build-caching [1 comments, 2 participants]