[Cache] Update always-online.mdx

[luishcardoso]

Summary

Can we add the docs here for further info on 5XX?

https://developers.cloudflare.com/support/troubleshooting/general-troubleshooting/troubleshooting-crawl-errors/#http-5xx-errors

Thanks.

[cloudflare-docs-bot]

Review

⚠️ 2 warnings found in commit 9b77a87.

👉 Fix in your agent 👈

Fix the following review findings in PR #32657 (https://github.com/cloudflare/cloudflare-docs/pull/32657).

Before making changes, review each finding and present a brief summary table:
- For each finding, state whether you agree, disagree, or need clarification
- If you disagree (e.g. the fix requires disproportionate effort for minimal benefit,
  or the finding is factually incorrect), explain why
- If you need clarification before deciding, ask those questions
- Then share your plan for which issues to tackle and in what order

After triaging, follow this order:
1. Post a comment on this PR for any findings you are skipping, with the finding ID and your reasoning.
2. Then commit the fixes for the legitimate findings.

The comment must come before the commit — the bot reads PR comments when a new
push triggers a review, so skip comments posted after the push will be missed.

---

## Code Review

### Warnings (1)

#### CR-a4ec31a2a6fa · Inconsistent status-code example
- **File:** `src/content/docs/cache/how-to/always-online.mdx` line 30
- **Issue:** The sentence uses 520 as an example of a 5XX returned while the origin is reachable, but the preceding paragraph states that 520–527 are generated by Cloudflare to indicate the origin is unreachable. This contradicts the page’s own explanation of 520.
- **Fix:** Replace the example with a true origin-originated 5XX code such as 500, 502, 503, or 504, or rephrase to avoid referencing 520 in the origin-reachable case.

---

## Style Guide Review

### Warnings (1)

#### SG-20292f0ad264 · HTTP status codes should use monospace
- **File:** `src/content/docs/cache/how-to/always-online.mdx` line 30
- **Issue:** Line uses `5XX` and `520` in prose without inline code formatting.
- **Fix:** Format HTTP status codes with backticks, e.g., `[`5XX`](/support/troubleshooting/general-troubleshooting/troubleshooting-crawl-errors/#http-5xx-errors)` and `` `520` ``.

Code Review

This code review is in beta and may not always be helpful — use your judgment.

Warnings (1)

File

Issue

cache/how-to/always-online.mdx line 30

Inconsistent status-code example — The sentence uses 520 as an example of a 5XX returned while the origin is reachable, but the preceding paragraph states that 520–527 are generated by Cloudflare to indicate the origin is unreachable. This contradicts the page’s own explanation of 520. Fix: Replace the example with a true origin-originated 5XX code such as 500, 502, 503, or 504, or rephrase to avoid referencing 520 in the origin-reachable case.

Conventions

_{No convention issues found.}

Style Guide Review

Warnings (1)

File	Issue
cache/how-to/always-online.mdx line 30	HTTP status codes should use monospace — Line uses 5XX and 520 in prose without inline code formatting. Fix: Format HTTP status codes with backticks, e.g., [5XX](/support/troubleshooting/general-troubleshooting/troubleshooting-crawl-errors/#http-5xx-errors) and `520`.

Commands

Only codeowners can run commands. Post a comment with the command to trigger it.

Command	Description
/review	Runs a review now. Incremental if a prior review exists, full if not.
/full-review	Re-reviews the entire PR diff from scratch, ignoring incremental history. Useful after a rebase, when you want a fresh review, or if the bot gets out of sync and reports issues that no longer exist.
/ignore-review-limit	Permanently lifts the 2-review automatic limit for this PR. Future pushes will trigger reviews as normal.
/disable-auto-review	Stops automatic reviews from triggering on future pushes to this PR. Codeowners can still run /review or /full-review manually.
/rebase	Rebases the PR branch against production. On conflict, attempts to resolve automatically using AI. Stops with an explanation if confidence is not high enough.

[github-actions]

Hey there, we've marked this pull request as stale because there's no recent activity on it. This label helps us identify PRs that might need updates (or to be closed out by our team if no longer relevant).