This is a cosmetic issue with AI Agent / NowAssist updates in the Activity stream. What's happening is the journal entry is being attributed with a "represented by" reference pointing to the NowAssist Skill Configuration record (sys_id: d808244de4df5650f877f4c9ef9e2dd5) rather than a human-readable user name, and the activity formatter doesn't resolve it to a friendly display value.
Here are a few approaches to address it:
1. Check the System User behind the AI Agent
Look at the sys_user record that the AI Agent is running as. Navigate to sys_user.list and find the user context used by NowAssist/AI Agent. Make sure it has a proper First Name and Last Name (e.g., "NowAssist" / "Virtual Agent") so the activity stream has something meaningful to display.
2. Inspect the Journal Entry directly
Go to sys_journal_field.list and filter for that record. Check the sys_created_by and look at whether there's a represented_by or similar extended attribute being stamped. The raw sys_id is likely being stored in a field that the activity formatter tries to resolve as a display value but fails because it points to sys_gen_ai_skill_config (not a sys_user record).
3. Activity Formatter / UI Component customization
If the above doesn't resolve it, you can look at customizing the activity stream rendering in Employee Center. The component responsible is typically sn-activity-stream or the workspace activity feed. You could add a mapping or override so that when the "represented by" resolves to a non-user table record, it falls back to a friendly label like "AI Agent" or "NowAssist" instead of the raw sys_id.
4. Feels like a product gap
The quickest short-term fix is usually option 1 — ensuring the system user that NowAssist runs under has a clean display name. Would you like help writing a script to trace exactly which user and "represented by" value is being written to sys_journal_field for those entries?
