fix(POR-22649): handle app-setup entity errors in notification-center

[cursor]

Changes

• Add try/catch around notification fetch on /notification-center so platform API failures (e.g. No entity type for app-setup found) show a user-friendly SilentError instead of an unhandled Next.js request error in Sentry
• Return early when the token lacks notificationId
• Use safeParse for in-product CTA params and show a clear message when the notification is not task-linked

Testing Criteria

• Verified yarn lint:check passes on the changed file
• Change follows the same defensive pattern as POR-22642/22643/22646/22647 notification-center fixes

Notes

• The No entity type for app-setup found error originates from the Assembly platform notification service when an IU opens an in-product notification whose entity type is app-setup (app installation/setup notifications). Tasks app only handles task-linked notifications; this PR prevents the platform error from surfacing as a Sentry production alert.
• Manual follow-up: inspect the Sentry event in the Tasks project for workspace/notification ID and verify whether the notification was created for a non-task entity type (app-setup).

Impact & Surface Area of Change

• /notification-center page only — error handling for notification deep-link redirects

  

[linear-code]

POR-22649

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