fix: handle webhook-race on Premium Geo DB addon enable

[lohanidamodar]

When enabling the Premium Geo DB addon, the Stripe webhook can activate the addon and mark its invoice succeeded just before the console's explicit confirmAddonPayment call. The backend then can't find a pending invoice and returns billing_invoice_not_found (HTTP 404) — even though the addon is already enabled and charged.

The enable modal's catch only special-cased 409, so this benign race surfaced a confusing "Invoice no longer exists" error to the user despite success.

This tolerates the race 404 (billing_invoice_not_found / addon_not_found) on the inline confirm — re-syncing state and reporting success — mirroring the existing handling in premiumGeoDB.svelte's confirmAddon.

[appwrite]

Console (appwrite/console)

Project ID: 688b7bf400350cbd60e9

Sites (1)

Site	Status	Logs	Preview	QR
console-stage 688b7cf6003b1842c9dc	Processing	View Logs	Preview URL

Tip

GraphQL API works alongside REST and WebSocket protocols

[greptile-apps]

Greptile Summary

This PR fixes a confusing UX bug where the Premium Geo DB enable modal would surface an "Invoice no longer exists" error when the Stripe webhook activated the addon just before the console's explicit confirmAddonPayment call. The fix is a focused error-handling change.

• Wraps the confirmAddonPayment call in a try/catch that swallows 404 errors with types billing_invoice_not_found or addon_not_found, treating them as a successful race rather than a failure.
• State invalidation and the success notification still fire after a swallowed 404, keeping the UI consistent with the actual backend state.
• The pattern precisely mirrors the existing guard already present in premiumGeoDB.svelte's confirmAddon function, maintaining consistency across both enable paths.

Confidence Score: 5/5

Safe to merge — the change is a narrow error-handling addition with no impact on the happy path.

The change wraps a single API call in a try/catch and swallows only the two specific error types the PR targets, matching the identical guard already in use elsewhere in the same settings directory. State invalidation and the success notification still run after a caught error, so the UI stays consistent with actual backend state. No new code paths are introduced and the existing 409 handling is untouched.

No files require special attention.

Important Files Changed

Filename	Overview
src/routes/(console)/project-[region]-[project]/settings/premiumGeoDBEnableModal.svelte	Wraps confirmAddonPayment in a try/catch that swallows 404 errors with types billing_invoice_not_found or addon_not_found, mirroring the pattern already used in premiumGeoDB.svelte to tolerate the Stripe webhook race condition.

_{Reviews (1): Last reviewed commit: "fix(premiumGeoDB): treat webhook-race 40..." | Re-trigger Greptile}