Quiet expected upgrade-preview 400s in Sentry

[j-ruda-guardian]

Current situation/background

https://the-guardian.sentry.io/issues/7303821377/?environment=theguardian.com&project=1208603&query=is%3Aunresolved&referrer=issue-stream&sort=freq

Treat Digital Plus upgrade-preview 400 responses as expected ineligibility (null) instead of throwing. Keep showing the existing “not eligible” UI, and only report unexpected failures (e.g. 5xx) to Sentry

[Copilot]

Pull request overview

This PR reduces Sentry noise by treating Digital Plus upgrade-preview HTTP 400 responses as an expected “ineligible for online upgrade” outcome (returning null) rather than throwing, while still surfacing unexpected failures (e.g., 5xx) as errors.

Changes:

• Updated fetchUpgradePreviewData to return null for HTTP 400 (expected ineligibility) and only throw for other non-OK responses.
• Adjusted upgrade preview consumers to handle a null preview response (deep-link loader redirects; upgrade preview hook sets an error state for UI).

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.

File	Description
client/utilities/productUtils.ts	Returns null for upgrade-preview 400s to avoid throwing/capturing expected ineligibility in Sentry.
client/utilities/hooks/useUpgradeProductLoader.ts	Handles null preview by redirecting when deep-linking into the upgrade flow.
client/utilities/hooks/useUpgradePreview.ts	Handles null preview response by setting preview error state (used to show the “not eligible” UI).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[github-actions]

Deploy build 1973 of support::manage-frontend to CODE

All deployment options

• Deploy build 1973 of support::manage-frontend to CODE
• Deploy parts of build 1973 to CODE by previewing it first
• What's on CODE right now?

---

From guardian/actions-riff-raff.

[Copilot]

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

Comments suppressed due to low confidence (1)

client/utilities/productUtils.ts:282

• fetchUpgradePreviewData can now return null for an expected 400/ineligible response, but the function name still implies it always returns preview data. Consider renaming to make the nullable contract explicit so future call sites don’t forget to handle null.

export const fetchUpgradePreviewData = async (params: {
	subscriptionId: string;
	isTestUser: boolean;
}): Promise<UpgradePreviewResponse | null> => {
	const response = await changePlanFetch({

[github-actions]

Deploy build 1973 of support::help-centre to CODE

All deployment options

• Deploy build 1973 of support::help-centre to CODE
• Deploy parts of build 1973 to CODE by previewing it first
• What's on CODE right now?

---

From guardian/actions-riff-raff.