You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
agent preview start --authoring-bundle crashes for AgentforceEmployeeAgent without default_agent_user (reading 'replace') #3676
sf agent preview start --authoring-bundle <name> crashes for an Agent Script agent of type AgentforceEmployeeAgent that has no default_agent_user in its config block (employee agents run as the logged-in user, so this field is not set).
defaultAgentUser is undefined for employee agents without default_agent_user. A guard such as (defaultAgentUser ?? '') — or skipping the user lookup when it is undefined, since bypassUser is forced to false for AgentforceEmployeeAgent a few lines later anyway — would fix it.
We have determined that the issue you reported exists in code owned by another team that uses only the official support channels. To ensure that your issue is addressed, open an official Salesforce customer support ticket with a link to this issue. We encourage anyone experiencing this issue to do the same to increase the priority. We will keep this issue open for the community to collaborate on.
hi @joananwolfcobracrm - the team acknowledged this, and already has a fix on its way! Should be available next Wednesday, try nightly or latest-rc to confirm!
Activity
git2gus commentedon Oct 30, 2026
This issue has been linked to a new work item: W-24726042
github-actions commentedon Oct 30, 2026
We have determined that the issue you reported exists in code owned by another team that uses only the official support channels. To ensure that your issue is addressed, open an official Salesforce customer support ticket with a link to this issue. We encourage anyone experiencing this issue to do the same to increase the priority. We will keep this issue open for the community to collaborate on.
WillieRuemmele commentedon Oct 30, 2026
hi @joananwolfcobracrm - the team acknowledged this, and already has a fix on its way! Should be available next Wednesday, try
nightlyorlatest-rcto confirm!