@Mention bell notifications open a "page not found" link (/now/cwf/agent) when Configurable Workspace is not in useIssue When a user is @mentioned in a work note or comment, an entry appears in the notification bell (Next Experience / Polaris UI). Clicking that entry navigates to a broken page at /now/cwf/agent instead of opening the record where the user was mentioned. The related @mention email notification is not affected, and other bell notifications such as assignment notifications work normally. Symptoms A user is @mentioned in a work note or comment on a record.The user opens the notification bell and sees “You have been mentioned by...” for that record.Clicking the notification navigates to the URL path /now/cwf/agent and returns a “page not found” error.The issue is reproducible across production and sub-production instances.The issue is typically noticed after an upgrade, when @mention entries begin to appear in the bell for Next Experience users.Deactivating the Send Notification business rule on live_notification, or adding business rules on ui_notification_inbox, does not fix or suppress the bell entry.Preventing the bell entry through custom logic against GlideNotificationBroadcaster does not work, because the API is internal, undocumented, and ignores table and document overrides. Release You can expect to see it when all of the following are true: The instance uses Next Experience (Polaris) with the notification bell enabled.Users work in the standard Platform UI and Configurable Workspace (Agent Workspace) is not configured or accessible at /now/cwf/agent.The out-of-the-box @mention handler and Send Notification business rule on live_notification are unmodified. Cause The out-of-the-box @mention handler (a script include that builds the live notification) hardcodes the link target to the Configurable Workspace route (now/cwf/agent) and sets the notification target to the live_notification record itself rather than the record on which the user was mentioned. The ui_notification_inbox entry therefore points to live_notification, which resolves to the Agent Workspace route. If the instance uses the standard Platform UI rather than Configurable Workspace, that route is not configured and the link fails. This is OOTB behavior that assumes Configurable Workspace is in use. It is not caused by customer configuration, and the bell entry is created by the platform notification engine independently of the Send Notification business rule. Resolution Option 1 (recommended when links should open in the Platform UI): update the OOTB @mention script include so the notification points to the source record in the Platform UI. Before editing, export the original script include as XML so it can be restored and compared after upgrades. Locate the script include that creates the live notification for @mentions (System Definition > Script Includes) and change three values: a) Target record. Change the target from the live notification context to the source record.Before: notificationGR.setValue(“target”, context.sysId);After: notificationGR.setValue(“target”, context.recordSysId); b) Target table. Change the target table from live_notification to the source record’s table.Before: notificationGR.setValue(“target_table”, “live_notification”);After: notificationGR.setValue(“target_table”, context.tableName); c) Navigation path. Replace the hardcoded workspace path with a Platform UI path.Before: “path”: “now/cwf/agent”After: “path”: “now/nav/ui/classic/params/target/” + context.tableName + “.do%3Fsys_id%3D” + context.recordSysId Save the change and test by @mentioning a user on a record, then clicking the resulting bell notification. It should open the record in the Platform UI. Notes: Exact variable names and line numbers vary by release, so compare against your own version of the script. Because this modifies an OOTB record, it will appear as a customization and may be skipped or flagged during upgrades. Re-validate after each upgrade. Option 2 (if the bell @mention entries are not wanted): users can unsubscribe from the bell channel of the Activity Stream @Mention Email notification in their notification preferences. This is per user and is not a scalable admin-level fix. Option 3 (custom event approach): inactivate the OOTB Send Notification business rule on live_notification, then create an event registration, an async business rule on live_notification that queues a custom event against the referenced record (not the live_notification record), and a provider notification triggered by that event with the recipient taken from event.parm1. Note that inactivating the OOTB rule suppresses the default bell entry for all @mentions.