not able to find Case comment relatedlist in the prompt builder.
#Trailhead Challenges
not able to find Case comment relatedlist in the prompt builder.
#Trailhead Challenges
Hi @CHAITANY POTEKAR This error (OAUTH_APPROVAL_ERROR_GENERIC) usually occurs when Salesforce cannot complete the OAuth authentication request from Postman.
I would suggest checking these points:
Start by checking the Client ID and Callback URL. Also, review Salesforce Login History for more details. Once corrected, try generating a new access token.
Related Official Documentation:
Hope this helps!
Hello Trailblazer Community,
I am learning Salesforce Administration and building a Recruitment Management project in my Trailhead Playground.
In Setup → Login History, I repeatedly see the error “Failed: Missing Consumer Key Parameter.”
Here are the details:
I have already created a Salesforce Trailhead Support case to investigate this issue.
My questions:
I have not intentionally configured any new integrations to address this error. I will appreciate any suggestions. Thank you!
#Trailhead Challenges
Hi @Mohsin Azam The Missing Consumer Key Parameter error usually happens when an OAuth authentication request is missing the required Consumer Key (Client ID).
Since your Trailhead Playground is working fine, it may be related to a separate Trailhead authentication attempt.
I would suggest checking these points:
Continue working on your project and monitor the errors. No need to create a new Playground unless access issues occur.
Related Salesforce Documentation:
Hope this helps!
Hello,
I have hit a wall when it comes to deploying my agent as part of the Headless Use Case Trail. I keep getting the attached error message, can anyone advise?
Thanks in advance
#Help #Trailhead Challenges #Agentforce
Hi @George HuitsonThis error indicates that Salesforce is unable to publish the agent because changes to Bot Version v1 are currently restricted. Since Agent Script compilation completed successfully, the issue appears to be related to publishing rather than the script itself.
I would suggest checking these points:
Since Headless 360 is a beta feature, this could be a platform-side issue. Avoid changing the Agent Script unnecessarily when compilation is successful.
Related Official Links:
Hope this helps!
Hi @Sneha Sharma Welcome to the Salesforce Trailblazer Community!
You can register for free on Trailhead and start preparing for Salesforce certification.
Here are some useful official resources:
Start with the beginner modules, complete hands-on challenges, follow the certification study plan, and then register for the exam.
All the best for your Salesforce learning journey!
We couldn’t find a role named 'Customer Support Rep'.
what is this error
#Trailhead Challenges
Hi @salman khan This error means Trailhead cannot find a role named Customer Support Rep in your selected Salesforce Playground.
Please check these steps:
Check the role name and selected Playground first. Even a small spelling difference can cause this error.
Hope this helps!
Hi All - I am on my way to be an Agentforce Legend, I have connect my org to slack and got approval from my salesforce org and even actuvated from slack appliaction as a new user what all are the steps that i am missing here.
1. Approval from slack done
2. Approval from Salesforce org done.
3. Install Packages used for slack.
4. Used necessary slack subagents and actions done.
Only the difference is the username used in Slack creation org is
Jone.done@gmail.com, where as while dealing with "Configure a Slack Agent in Salesforce" I am using email as Jone.slack@gmail.com
Following to the above i think agentforce should be approved in slack and activated which we are missing per Google AI
#Trailhead Challenges #Agentforce #Slack Developers
I'm unable to find the Reviews object setting when trying to create this permission set. Trailhead instructions:
Create a Permission Set
Create a permission set that controls access to the Review object for your Recruiter app.
@Mackenzie O'Connell You need to create the Reviews object yourself first and then it'll be available for permission setting. See below module
Share the screenshot of all users list page. Mention which user did you create.
On this trail, with the removal of Agentforce (Default) option I keep getting this error:
Agentforce (Default) isn’t enabled in your org. Be sure to turn it on in the Salesforce Go section of Setup and try again.
Einstein Set up and Agentforce Agents are active, and both were toggeled on and off. Anyone have another setting idea I can try, or maybe a combination of CLI commands?
#Trailhead Challenges