fix(POR-22657): handle platform product-not-found errors in notification-center

[cursor]

Changes

• Wrap /notification-center notification fetch in try/catch so platform API errors (e.g. not able to get product: code [not_found] error [Product not found]) show a user-friendly SilentError instead of an unhandled request error in Sentry
• Return early when token payload lacks notificationId or carries a non-UUID value
• Use safeParse for CTA params with a friendly message when the notification is not task-linked

Testing Criteria

• ESLint on changed file — no new issues
• Verified fix matches the established defensive pattern from POR-22642–POR-22654 (try/catch + SilentError + safeParse + UUID guard)

Notes

• Linear: POR-22657 — not able to get product: code [not_found] error [Product not found]
• The error string originates from the Assembly platform notification/product service when an IU opens an in-product notification whose linked product entity cannot be resolved (deleted product, wrong entity routing, or missing product record). Tasks cannot fix the platform data but can handle it gracefully.
• Manual follow-up: inspect the Sentry event in the Tasks project for workspace/notification ID and verify whether the notification was created for a product entity that Tasks does not handle.
• Related: POR-22642–POR-22654 / PRs fix(POR-22642): handle non-task notifications gracefully in notification-center #1409–fix(POR-22654): handle platform notification lookup errors in notification-center #1419 (same defensive pattern for other platform errors)

Impact & Surface Area of Change

• /notification-center server component only — IU notification deep-link entry point
• No API route or client component changes

  

[linear-code]

POR-22657

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
tasks-app	Ready	Preview	Aug 22, 2026 4:35am