@LIJ011, I am also facing the same issue, where you able to find any solution?

@LIJ011

to fix Pulse @tagging in 24.2. First, make sure Pulse is actually enabled on the case type and your users’ access roles allow posting and mentions. Confirm the people you’re trying to tag have active Operator IDs in the same application context (not disabled, not withdrawn access groups). Clear the browser cache and try a different browser to rule out client issues. Rebuild search indexes so operators and data are discoverable (full reindex of Data, Work, and Operator; verify real-time indexing is on). If you use Constellation, check that the Pulse widget is the latest version and that autocomplete for mentions isn’t blocked by any custom section or harness override. Review any relevant DSS or when-rules that toggle social features or mentions in your app and ensure they evaluate to true for your roles. Check for authorization issues in Tracer/Logs when you type @ (look for denied read on Operator, directory, or live search data pages). Finally, install the latest 24.2 platform patch for your stack; if the problem persists in a vanilla test app, open an SR with those findings so Support can provide a hotfix.