***POLL IS CLOSED***
Lantern Astro won across every poll and will be the Winter ’27 Release logo!
_________
Help us choose the official Salesforce Winter ’27 Release logo.
Which character should star?
1️⃣ Agent Astro
2️⃣ Bookish Codey
3️⃣ Agent Appy
4️⃣ Lantern Astro
Cast your vote here, or vote in our polls on X, Instagram and LinkedIn (or all four!).
🗳️ Voting closes Friday, July 10. The character with the most votes will become the official Salesforce Winter ’27 Release logo.
I'm trying to complete Agentblazer and ive completed 96% of the training I'm stuck as I cant see Agent on the Dev Edition which I created at the beginning of this training. Has anyone faced similar issue, I need to get this done sooner as my playground expires on 10th Aug
#Agentforce #Trailhead
Forum Ambassador
Hey @sachin shinde, if somehow it's not working, yes you can create a new org and redo the work there
But make sure Enistein and Agentforce is enabled in your org
Really enjoyed going through this Trailhead Quest on Setup with Agentforce ! 🚀
It’s a great hands-on way to get familiar with the different steps involved in setting up and working with Agentforce in Setup. I particularly liked that it gives you an opportunity to learn by actually configuring things rather than just going through theory.
A good starting point for anyone looking to get more practical exposure and understand how the different pieces fit together.
#Salesforce #Agentforce #Trailhead Challenges #Trailhead #AI #SetupWithAgentforce #SFSweepstakes
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.
#Trailhead Challenges #Trailhead #Agentforce #Agentblazer
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:
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!
#Agentforce
Hi,
Things worth checking given your setup:
1. Since this only fails on Committed versions and not Draft, compare what's different structurally — specifically check if your DSL config references anything environment-specific (Data Cloud retriever target URIs, endpoint variables like the {{DOMAIN}} placeholder visible in your Postman body) that might resolve correctly in the live Draft context but fail to resolve/bind correctly once "frozen" into a Committed version.
2. Check whether the {{DOMAIN}} placeholder in your instanceConfig.endpoint is actually being substituted with a real value before the request goes out — if that's still literally the placeholder string when hitting the API (rather than your actual instance domain), that alone would produce exactly this kind of config validation failure.
3. If you're testing this in a sandbox, confirm metadata sync between the sandbox and any connected Data Cloud org is fully complete — partial/lagging metadata sync between environments is a known category of "config looks fine in UI but fails at runtime" issues in Agentforce, even if I can't point to a specific KB article confirming this exact error string.
If nothing works,
1. File a case with Salesforce Support, explicitly including both pieces of evidence — the native Live Test failure screenshot AND the Postman reproduction — since showing it fails through Salesforce's own UI (not just a custom API call) makes this much harder to dismiss as a client-side config issue on your end.
2. Reference the exact error payload (AgentApiException, requestId, timestamp) from your screenshot — that requestId in particular will let their engineering team pull server-side logs for that specific failed request.
3. Ask specifically whether this is a known issue with agentDSLEnabled + Committed versions, since that's a fairly new/narrow combination and may not be broadly tested yet.
Just wrapped up the Setup with Agentforce for Admins quest! 🥳
Current mood: 57% to 100% here for the free gift. 💸🎁 Your move, Trailhead team! 😉Good Quest..Easssy for the Admin permission who need to intract with AI. Nice One...Trailhed
Hi everyone,
I'm looking for some guidance on preventing duplicate Account records.
I found two Account records with different names but the same VAT number. This should not be allowed for records with the same record type.
Having the same VAT number across different record types is acceptable.
In addition to the VAT number, duplicate values should also not be allowed for any of the fields listed below.
I tried to solve this using a Duplicate Rule and Matching Rule, but it did not help. I was able to create the Duplicate Rule, but when configuring the Matching Rule, I could not find the Record Type
field in the matching criteria conditions.
#Trailhead Challenges #Salesforce Developer #Salesforce Admin #Agentforce #Trailhead #Flow #TrailblazerCommunity
Yes, Its good to implement workaround using flow. You may combine the duplicate rule along with flow in a way that record type field part is done by flow and rest of the part is done matching rule. A custom field can be set to true in flow and it can be checked in the dup rule.
Hello team,
I have created my trailhead account and tried to join tha trailblazer community group using tha provide link.however ,I am unable to join the group.colud you please help me resolve this issue? thankyou
#Agentforce
Hi everyone,
I'm encountering an issue where an Employee Service Agent fails during session initialization in Live Preview, but only after committing a version that includes an Apex Invocable Action.
Here is the exact setup and breakdown of the behavior:
Context & Setup
Steps to Reproduce
Error Log (Network Tab): The request to https://api.salesforce.com/einstein/ai-agent/v1/agents/{AgentId}/sessions returns a 500 Internal Server Error, containing the root exception:
{ "status": 500, "path": "v6.0.0/agents/{AgentId}/sessions", "mode": "preview", "requestId": "7c375608-b352-48d1-8895-dd65dbcb1874", "error": "AgentApiException", "message": "Internal Server Error: org.springframework.web.reactive.function.client.WebClientResponseException$UnprocessableEntity: 422 Unprocessable Entity from POST https://api.salesforce.com:9443/einstein/copilot/v1/planner/{PlannerId}/sessions", "timestamp": 1785923824404, "expected": false, "details": null}Key Isolation Observations
Has anyone encountered this issue where the GenAiPlanner fails to resolve action schemas specifically on Committed versions for a particular Org? Is there a way to flush/force-sync the Einstein Planner Engine cache?
Thanks for any insights!
#Agentforce
As I'm developing an agent that performs record DML and queries of records the current(human) user has access, but will be returned when trying from the agent interface? Whose access is applied in this scenario?
#Agentforce
,
The short answer: it depends on whether the channel your agent is deployed on requires an authenticated Salesforce session — not on the agent type itself, though the type strongly correlates with it in practice.
1. Authenticated channels (Lightning Experience/Mobile, internal Slack, an internal portal where the user is logged in) — the agent runs in the context of the logged-in human user. Your normal Salesforce access controls apply exactly as they would if the user clicked around manually: profile/permission set object & field-level security, sharing rules, role hierarchy, OWD. Whatever that user can query or DML, the agent can — nothing more, nothing less. If you're testing from the Agentforce panel inside Lightning while logged in as yourself, your own access is what's being applied.
2. Unauthenticated channels (public Messaging, embedded chat widgets, email) — there's no human session to inherit from, so Salesforce falls back to a dedicated Agent User: a special integration-type Salesforce user (License: Einstein Agent, Profile: Einstein Agent User) that you configure explicitly in Agent Creator. Here, the agent user's
permission sets, field-level security, and sharing access govern everything — completely independent of what the anonymous customer typing into the chat could see.
Hope this helps.