When a Conversational Agent is triggered through Autopilot in Slack, the 'Identity' field in the Orchestrator Job Details tab always shows a single account (an unattended robot service account) instead of the Slack user who started the agent. Is this expected, and where can I find the user who triggered the agent?
Summary
A Conversational Agent is started from Slack through Autopilot. Even when different Slack users start the agent, the Identity field in the Orchestrator Job Details page shows the unattended robot service account that executed the job.
In some cases, the account shown in Identity may change. This happens because a different unattended robot may execute the job.
The Slack user who started the agent is not shown in the Identity field. Instead, their email address is available in the execution trace in the cloudUserEmail field.
Resolution
This is expected behavior.
The Identity field shows the account that executed the job, not the user who started it. Since Conversational Agents run using an unattended robot service account, that account is displayed in the Identity field.
To find out who started the agent from Slack:
- Navigate to Orchestrator, then click on 'Folders', then click on 'Auotmations'
- Click on 'Jobs' and identify the job pertaining to the Conversational Agent.
- Click on the information icon at the end of the row and this will open the Job Details
- Click on the 'Trace' tab to access the UserMessage entries
- Click on a UserMessage entry and read the Metadata to identify the cloudUserEmail field. The value is the identity of the Slack user who used the Conversational Agent.