Agentforce behavior issues occur when an agent is active and accessible, but its responses or execution do not match expectations.
Common scenarios include:
These issues are usually caused by configuration or setup rather than system errors.
This article provides a self-service troubleshooting guide to help you identify and resolve common Agentforce behavior issues using Agent Builder, configuration settings, and setup validation
When Agentforce behavior is unexpected, always follow this order:
Most issues fall into one of the following categories:
Prompting issues are the most frequent cause of unexpected Agentforce behavior. Unlike deterministic systems such as traditional Einstein Bots, LLM-based agents can behave unpredictably if prompts are unclear or inconsistent.
Agent behavior is influenced by prompts defined in:
Subagent descriptions
Subagent instructions
Action descriptions
Action input descriptions
Action output descriptions
Use explicit and unambiguous language in Subagent and Action descriptions
Avoid relying on the LLM to infer business rules
Clearly define when an Action should and should not be used
Ensure Action outputs are clearly structured and described
If conversations fail to start or display generic errors, validate the following setup items.
Toggle Agentforce
Navigate to Setup → Einstein Copilot
Turn Agentforce off, save, then turn it back on
Toggle Einstein Bots
Navigate to Setup → Einstein Bots
Turn off, save, then turn on
Toggle Einstein Setup
Navigate to Setup → Einstein GPT Setup
Turn off, save, then turn on
Verify Default Agent Exists
Ensure “Enable the Agentforce (Default) Agent” is enabled
Toggle it off and on again if needed
Prompting issues
Topic or Action filters
Missing context variables
Permission restrictions
Topic and Action Filters
Confirm filters are correctly configured
Ensure required context variables exist before evaluation
Context variables must never be assumed or derived from prompt instructions.
They are not automatically available in Agent Builder and must always be explicitly set using deterministic mechanisms such as:
Action output mapping
Variable mapping in configuration
Flow or structured assignment logic
Do not rely on prompt instructions, Subagent instructions, or natural language reasoning to set or infer context variables.
Any logic that depends on context variables must ensure they are explicitly initialized before evaluation.
Citations are displayed only when:
The Knowledge Action returns citations
Citations are enabled for that Action
Open Knowledge Action configuration
Confirm citations are enabled
Test the Action independently
Ensure response is not overwritten later in the flow
Also verify:
Knowledge articles are published
Articles are indexed
Articles are accessible to the agent
| Area | Limit |
|---|---|
| LLM response | ~2048 tokens |
| Action output | ~65,000 characters |
Responses cut off mid-sentence
Missing sections in long outputs
Partial Action results
Use “Show in Conversation” instead of embedding large outputs
Avoid returning unnecessary fields in Actions
Break complex requests into multiple steps
Store large data in objects and reference via Actions
“Something went wrong” messages
Responses appear then get rewritten
Partial or inconsistent outputs
Review prompt templates for strict formatting (for example, JSON-heavy outputs)
Simplify complex or nested instructions
Reduce large Action outputs
Consider switching models if instability persists
Avoid generating large responses in a single turn
Break workflows into smaller steps
Define fallback responses to prevent repeated regeneration
If responses appear and then change or disappear, groundedness checks may be triggered.
Ensure instructions are accurate and specific
Avoid overly broad or ambiguous prompts
Ensure responses are grounded in Knowledge or structured data
Filtering logic excludes the Topic or Action
Permission restrictions
Missing configuration in agent setup
Review filter logic carefully
Ensure required context variables are set
Confirm Topic or Action is included in agent configuration
Validate permissions with administrator if needed
Some URLs may be hidden for security reasons.
Add trusted URLs in Setup → Trusted URLs
Ensure URLs are returned by Actions or explicitly allowed
Escalation may occur due to:
Agent unable to proceed
Escalation Topic selection
System limits reached
Review escalation logic and naming
Ensure fallback Topics exist
Validate escalation conditions are intentional
An agent can make up to 8 LLM calls per user turn.
Repeated Action failures
Validation loops
Overly complex workflows
Simplify Subagent flows
Reduce retry logic
Break workflows into multiple steps
Error Message:
“An error occurred when executing a flow interview”
Ensure the Service Agent User has:
Agentforce Service Agent Secure Base
Agentforce_Service_Agent permissions
Permission Set Group: AgentforceServiceAgentUserPsg
Permission Set License: Agentforce Service Agent User
If the agent responds in the wrong language:
Verify agent language configuration
Check org locale settings
Ensure prompts are language-consistent
Global Instructions define system-level behavior for Agentforce.
Maintain consistent tone and style
Define fallback behavior
Handle ambiguity
Manage sensitive scenarios
Address competitor mentions
Most Agentforce behavior issues are caused by configuration issues such as:
Overlapping Subagents
Unclear Action definitions
Conflicting instructions
Missing or unindexed Knowledge
Improving Subagent boundaries, Action clarity, and instruction design resolves the majority of issues
Best Practices for Agent User Permissions
Agentforce: How to Troubleshoot Common Agentforce Errors
005305511

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.