fix(POR-22666): handle platform FORM_RESPONSE errors in notification-center

[cursor]

Changes

• Wrap /notification-center notification fetch in try/catch so platform API errors (e.g. unable to perform action complete on FORM_RESPONSE) 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-22665 (try/catch + SilentError + safeParse)

Notes

• Linear: POR-22666 — unhandled request error: unable to perform action complete on FORM_RESPONSE
• The error string does not exist in tasks-app source or dependencies — it originates from the Assembly platform when loading notification details (platform state/authorization error attempting to complete a FORM_RESPONSE entity during notification resolution)
• Platform team should investigate why a notification references a form response that cannot be completed (e.g. already completed, deleted, wrong permissions, or orphaned entity reference)
• Same class of issue as other /notification-center platform errors (POR-22642–POR-22665)

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

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