fix(POR-22665): handle platform key-param errors in notification-center

[cursor]

Changes

• Wrap /notification-center notification fetch in try/catch so platform API errors (e.g. The key param is incorrect) show a user-friendly SilentError instead of an unhandled request error in Sentry
• Return early when token payload lacks notificationId
• 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
• TypeScript compiles for the changed file
• Verified fix matches the established defensive pattern from POR-22642–POR-22658 (try/catch + SilentError + safeParse)

Notes

• Linear: POR-22665 — unhandled request error: The key param is incorrect
• The error string does not exist in tasks-app source or dependencies — it originates from the Assembly platform when loading notification details (likely an invalid storage/resource key parameter during notification entity resolution)
• Platform team should investigate why a notification references a resource with an invalid key (manual intervention)
• Same class of issue as other /notification-center platform errors (POR-22642–POR-22663)

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-22665

[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:41am