I completed both validation rules exactly as instructed:
4 Antworten
Thanks , It's working now
Earlier this "Check box" was selected, As I deselect this check box and "check challenge" it's working.
#Trailhead Challenges2.024 diskutieren mit
- Letzte Aktivität
- Erstellt am
- Empfohlen
- Alle Fragen
- Fragen mit einer akzeptierten Antwort
- Unbeantwortete Fragen
- Fragen ohne akzeptierte Antwort
An unexpected error occurred while inserting Opportunity records and we couldn't check your work. Make sure Opportunity records can be inserted in this org, and click "Check Challenge" again. If this continues, contact the Trailhead Help team.
2 Antworten
This Trailhead error usually means the org can’t create Opportunity records because of validation rules, required fields, automation (Flow/Trigger), or missing permissions. Check that Opportunities are enabled, your user has “Create” access for Opportunity, and there are no custom validation rules or mandatory fields blocking record creation. Also review active Flows, Apex triggers, or Process Builder automations that may fail during insert. After fixing the issue, try “Check Challenge” again or use a fresh Trailhead Playground if the org is heavily customized.
Hello, I have finished all the steps but I always have the same error: We can't find the flow 'Notification: Case for Large Account'.
Hi everyone,
I am currently working on the "Quick Start: Agent Actions" (Connect a Flow to Agentforce with Actions) project, but I am stuck on the challenge verification step.
Even though I have completed all the steps successfully, I keep receiving the following error message:
Summary of what I did based on the instructions:
- Enabled Einstein and Agentforce (Default) in a new trial org.
- Opened the agent in the Agentforce Builder and added the General CRM topic.
- Created a new Custom Agent Action referencing the existing Initiate Return Flow with the exact instructions and inputs/outputs specified.
- Added the 'Initiate Return' action to the General CRM topic, ensured it saved properly, and successfully Activated the agent.
- Tested the interaction in the conversation window—the agent successfully fetched the order details and updated the Return Status field to 'Initiated' via the custom flow automation.
The issue: The instructions specifically guide me to use the existing "Agentforce (Default)" agent (and rename it from Einstein Copilot if necessary). However, the challenge validation error is asking for an agent named 'Order Agent'.
The unit instructions do not mention creating or renaming the agent to 'Order Agent'. I have double-checked that my agent is fully activated.
Has anyone else encountered this issue? Should I create a new agent named 'Order Agent' from scratch, or is there a discrepancy in the challenge requirements?
Any help or guidance would be greatly appreciated!
Thank you.
#Trailhead Challenges
4 Antworten
@Nari Kim This is a mismatch between the older instructions and the current challenge checker.
The challenge expects the prebuilt agent named Order Agent, not Agentforce (Default). In the updated steps, Trailhead says to open Agentforce Studio, go to Agents, and select Order Agent
.
Do not continue with the old Agentforce (Default) agent for this challenge. Open the special Developer Edition org from the badge, find Order Agent, add the General CRM subagent, create/add the Initiate Return action under that subagent, then Commit Version and Activate the agent.
If Order Agent is not available in the org, that usually means the org is not the correct special DE org for this badge, or it was created before the badge content was updated. Create a fresh org from the sign-up link in the same Trailhead unit and reconnect that org to Trailhead.
Relatable post: https://trailhead.salesforce.com/trailblazer-community/feed/0D5KX00000j9Qod0AE
Im getting the error
"We can’t find the decision element ‘Large Account?’ with API Name ‘Large_Account?’ in the 'Notification: Case for Large Account' flow."
even though you cant put question marks in api names. I still set the label name correct but ofcourse I cant name the api that also I double checked the flow name and everything.
#Trailhead Challenges
Step not yet complete in Agentforce
We can't find the Get Customer Details action. Make sure it has been created and has an API Name of 'Get_Customer_Details'.
I am getting this error again and again... I did 2 times once according to the instruction and the next from myself . but same error again and again ...
what should i do...?
#Trailhead Challenges
1 Antwort
The error "We can't find the Get Customer Details action. Make sure it has been created and has an API Name of 'Get_Customer_Details'" means Agentforce cannot locate the Flow or Apex action with that specific API name.
Steps to resolve:
- Go to Setup [arrow] Process Automation [arrow] Flows. Look for a Flow named "Get Customer Details".
- Confirm the Flow's API Name is exactly Get_Customer_Details (underscores, not spaces, and exact capitalization matters).
- If the Flow exists but has a different API name, click the Flow, open Flow Properties, and update the API Name to Get_Customer_Details. Then save and activate it.
- If the Flow does not exist, follow the badge instructions to create it from scratch. Make sure to set the API Name to Get_Customer_Details exactly as specified.
- After correcting the API name, go back to the Agentforce Agent builder, re-open the action, confirm the action references Get_Customer_Details, and then return to Trailhead to re-verify the step.
Common mistakes: Using a space instead of underscore, different capitalization, or not activating the Flow after saving.
Hi everyone,
I’m trying to set up automatic task assignments in Salesforce based on specific criteria (like region or department). I’m not sure whether to use Flow, Process Builder, or something else.
Has anyone done this before? Any tips or step-by-step guidance would be super helpful!
Thanks in advance!
#Trailhead Challenges
3 Antworten
Hi , @tom smite
Use Flow for this. Process Builder is legacy and shouldn’t be used for new automation.
Short approach:
- Create a Record-Triggered Flow on the object where the task should be assigned.
- Add Decision logic for criteria like Region or Department.
- Use Assignment or Create Records to set the right owner or create the task.
- Test with different sample records before activating.