#Agentforce555 utenti parlano di questo argomento

Hi community,

We are encountering a page-blocking "412 Precondition Failed" error when attempting to use or preview any Committed version of our DSL-enabled Agentforce Service Agent (agentDSLEnabled set to true).

Symptoms:

1. Draft editor works fine: We can make changes to the agent Draft in the Agentforce Builder without issues.
2. Committed versions fail: As soon as we select any Committed version (e.g., Version 1 Committed) in the Builder, the Preview chat panel fails to connect and displays: "Something went wrong. Refresh and try again."
3. Console/API Error: Inspecting the browser console shows that the background session call returns:
   • Endpoint: /services/data/v61.0/einstein/ai-agent/v1/agents/{agentId}/sessions (also fails with the same error on the external sessions API via Postman).
   • Response Code: 412 Precondition Failed
   • Error Message: {"message":"Unable to load agent config: Invalid Config"}

Has anyone else run into this issue where the compiler or orchestrator fails to load/resolve the config only for Committed versions? Is this related to Data Cloud retriever target URIs or sandbox metadata sync issues?

Any advice or workarounds would be highly appreciated. Thanks! 

I am working on the Trailhead project:

Build Your First Sales Coach

Configure and Activate Your Sales Coaching Agent

The challenge validation fails with the following error:

[Sales Coach Agent] does not contain

[Agentforce Sales Coach: Opportunity Coaching].

Current configuration:

- Sales Coach Agent is Active

- Developer Name: Sales_Coach_Agent

- Locale: English (United States)

- Language: English

- Topic Selector subagent exists

- OpportunityCoaching subagent exists

- NegotiationRolePlay subagent exists

- ProposalRolePlay subagent exists

OpportunityCoaching contains all four standard feedback actions:

- Give Feedback on Qualification Stage

- Give Feedback on Needs Analysis Stage

- Give Feedback on Negotiation/Review Stage

- Give Feedback on Proposal Stage

The current Agentforce Builder uses Subagents instead of Topics.

The validator still reports:

"[Sales Coach Agent] does not contain [Agentforce Sales Coach: Opportunity Coaching] topic."

Has anyone encountered this recently? Is this a known validator issue or is there an additional configuration required in the current Agentforce Builder UI?

Thank you. 

Hi all — I'm trying to start a session with the Agent API and consistently get an HTTP 404 with an empty body. Authentication works, the agent is active, and every documented 404 cause seems ruled out. Looking for help on whether the Agent API is provisioned on my org, or what I'm missing. 

What I'm calling 

POST

Authorization: Bearer <token>   (via Named Credential) 

Content-Type: application/json 

{ 

  "externalSessionKey": "pf-test-<uuid>", 

  "instanceConfig": { "endpoint": "

" }, 

  "streamingCapabilities": { "chunkTypes": ["Text"] }, 

  "bypassUser": true 

} 

Response 

HTTP 404 

Headers: date, content-length, connection 

Body: (empty) 

Note: it's a bare 404 from the

gateway — n token gives 401, and a wrong agent id (with the API reachable) gives a JSON error such as EngineConfigLookupException. Here the body is completely empty, which suggests the path itself isn't served for my org. 

What I've verified (all OK) 

- Agent is Activated, type ExternalCopilot (custom agent, not "Agentforce (Default)"). Agent Id 0Xxg5000000wKO9CAM taken from the Agent Builder / BotDefinition. 

- OAuth: External Client App with Client Credentials flow, sc. Run-As user = System Administrator (full Agentforcepermissions). Token is issued successfully (auth is not the problem — no 401). 

- External Credential (OAuth 2.0, Client Credentials with Client Secret) + Named Credential → URL

, Generate Authorization Header enabled. 

- My Domain passed in instanceConfig.endpoint is the correct *.

host (confirmed via URL.getOrgDomainUrl()). 

- Agent reactivated and waited for propagation — no change. 

- Added Agentforce permission sets to the running user — no change. 

Things I could NOT find in Setup 

- No "Agent API" / "Einstein Agent API" enablement toggle any 

- In Agent Builder → Connections, the only options are Enhanced Chat v2 and Messaging (both "Needs Setup"); Messaging for In-App and Web is not available (no Digital Engagement license on this org). There is no "API" connection option, and Add Connections shows an empty asset list. 

Environment 

- Agentforce Developer Edition org (orgfarm dev-ed). 

- Calling the Agent API from Apex (server-side callout via Na 

Questions 

1. Is the Agent API (/einstein/ai-agent/v1) provisioned/enablition orgs? If not, how do I enable it? 

2. Does the Agent API require an explicit connection/channel on the agent (beyond Activation)? If so, which one — given "Messaging for In-App and Web" isn't licensed here? 

3. Is a bare empty-body 404 from

a known sned for this org" vs. a config issue? 

Thanks in advance — happy to share more logs/config. 

hi all im facing this issue from last 3 days i raised salesforce case as well bt no help from them this error im getting i connected with salsforce and slak all setting is correct  

I've tried many times to create a developper sanbox from this link : Developer Edition org with the product specialist agent

in the challenge : Prepare Your Agentforce and Slack Orgs.  

I did not receive any Verify email as it supposed to be. I have no error, no logs. Nothing to analyse.  

Only this picture :  

Do you have any idea of the issue please ? I am not able to complete this challenge. Thanks for your help !