Refine Your Prompt Template for Accurate Agent Replies - I have tried a few orgs but still missing the flow required to pass this trailhead.
#Trailhead Challenges
답변을 작성하세요...
0/9000
#Trailhead Challenges토론 중인 항목 1,896개
- 최근 활동
- 생성 날짜
- 추천 항목
- 모든 질문
- 인정받은 답변이 있는 질문
- 미답변 질문
- 인정받은 답변이 없는 질문
Error says : it is not activated and the type is not Flex
답변 1개
That error is the grader telling you two specific things about your agent: it must be Active, and its Type must be Flex.
1. Type = Flex: this step expects an Agentforce (Flex) agent, not a Service Agent template or another type. In Agent Builder, check the agent's type — if it is not Flex, create a new agent and choose the Flex (general/customizable) type, then rebuild your topic and actions on it.
2. Activate it: open the agent in Agent Builder and set it to Active (the Activation toggle / Activate button). The grader only sees it once the status is Active.
Two prerequisites that quietly block activation:
- You must be in the special Agentforce-enabled Developer Edition org for this badge, with Einstein turned on (Setup, Einstein Setup, On).
- Any Flow you added as an agent action must itself be Active, or the agent will not activate.
Fix the type and activate, then recheck.
if this helps, please mark it as the Best Answer so it helps the next person — thanks 🙂
답변 3개
We couldn’t find the new opportunity with the correct information. Ensure that you have entered the opportunity information correctly.
Hi, Im trying to finish this challenge but I keep getting this generic error:
Tried deleting and recreating the search index but it did not work.
Does someone have any advice to solve this problem?
#Trailhead Challenges
답변 1개
You do this from the hands-on org picker, not a separate settings page:
1. Open any hands-on challenge or project step (the Agentforce project you are working on is fine).
2. Click the name of your current playground/org shown near the Launch button, then click Manage Orgs (Manage Hands-on Orgs).
3. In that list you will see all your connected playgrounds, including the old Agentforce Builder Playground. Use the disconnect/remove option next to it.
Once it is removed it frees a slot, and you can launch or connect a fresh org for the project. Note Trailhead playgrounds also auto-expire after a stretch of inactivity, so an unused one will eventually drop off on its own too.
if this helps, please mark it as the Best Answer so it helps the next person — thanks 🙂
Body: I’m stuck on the Trailhead challenge “Handle Field Access with a Permission Set” (Recruiting app). The checker reports it can’t find a permission set that grants read/edit on all Job Application fields except Position and Candidate (read-only). I’d appreciate guidance on what I’m missing.
Requirements I’m following:
Create a permission set:
Label: Manage Job Applications
API Name: Manage_Job_Applications
License: None
Job Application object permissions: Read, Edit (no Create/Delete/View All/Modify All)
Field-level security on Job Application: all fields readable and editable, except Position and Candidate (read-only)
What I configured:
Permission Set
Label/API/License match the spec: Label “Manage Job Applications”, API Name “Manage_Job_Applications”, License “None”.
Object Settings > Job Application:
Object Permissions: Read and Edit only; Create/Delete/View All/Modify All are unchecked.
Field Permissions:
I enabled Read and Edit for all fields, then unchecked Edit only for Position and Candidate, keeping Read checked.
I re-verified that every other field has Edit=ON, and Position/Candidate have Edit=OFF.
Job Application object definition
Label: Job Application; Plural: Job Applications
API Name: Job_Application
Record Name: Job Application Name (Auto Number; Display Format: JA-{0000})
Optional features: Allow Reports=On, Track Field History=On; Allow Activities/Allow in Chatter Groups/Enable Licensing=Off
Classification: Allow Sharing=On; Allow Bulk API Access=On; Allow Streaming API Access=On
Deployment Status: Deployed=On
Search Status: Allow Search=Off (can turn On if required)
Org Language/Locale: Language=English; Locale=United States
Fields on Job Application
Position (API: Position__c): Lookup (or Master-Detail) to the Position object.
Candidate (API: Candidate__c): Lookup to the Candidate object.
Both are English labels/API names. I did not create similarly named extra fields (e.g., Position_Lookup__c).
Profiles/Assignments
Error message (excerpt): “Couldn’t find the ‘Manage Job Applications’ permission set that grants read and edit access to all Job Application fields except Position and Candidate.”
Troubleshooting already done:
Switched org Language/Locale to English/United States, waited a few minutes, and re-ran the check.
Reconfirmed Job Application > Field Permissions: Position/Candidate are Read=On, Edit=Off; all others Read/Edit=On.
Reconfirmed object permissions are exactly Read+Edit only.
Verified Position/Candidate field data types and lookup targets.
Ensured there are no duplicate or similarly named fields.
Verified object labels and API names conform to the spec.
Open questions:
Does the checker require an actual user assignment of the permission set?
Are there any other commonly missed toggles (e.g., View All/Modify All flipped on elsewhere, permission set group interactions, metadata propagation delays)?
What I can provide:
Screenshot of the permission set (Manage Job Applications) > Object Settings > Job Application > Field Permissions showing Position/Candidate Edit=Off and all others Edit=On.
Job Application Fields & Relationships list (with Position__c/Candidate__c types and lookup targets).
Org Language/Locale settings.
User permission summaries if needed.
Goal: Identify the minimum changes needed for the checker to pass (e.g., turning on Allow Search, changing Record Name to Text, assigning the permission set), so I can re-run the challenge successfully.
Thanks in advance for your help and any insights!
#Trailhead Challenges
답변 1개
The wording can not find a permission set that grants... is the clue — the grader looks the set up by API name first, then checks the field pattern. Two things trip most people here:
1. The API name must be exactly Manage_Job_Applications (underscores, not spaces). If it is even slightly different the grader cannot find it and reports exactly that message. Open the permission set and confirm the API Name reads Manage_Job_Applications.
2. Position and Candidate must be Read-only, meaning Read checked and Edit unchecked — not hidden. If you unchecked Read as well they count as not readable and the all-fields-readable check fails. Verify both show Read on, Edit off.
Also worth a quick pass:
- Every other Job Application field needs BOTH Read and Edit checked. Scroll the entire field list — a single field left without Edit fails it. (Any formula field can only be Read, and that is expected.)
- Object permissions: Read and Edit only, which you have — no Create, Delete, View All, or Modify All.
Nine times out of ten on this one it is the API name, or Position/Candidate being hidden instead of read-only. Fix that and recheck.
if this helps, please mark it as the Best Answer so it helps the next person — thanks 🙂
답변 3개
Hi Ibrahim, I had a similar issue. It may be that the Review custom object hasn't been created in your Playground yet. Try creating the Review object first, then return to the challenge and check whether the “Reviews” option appears. Hope this helps!
Hi everyone,
I'm currently working on the Become an Agentblazer Legend 2026 trail, specifically under the Unstructured Data in Data 360 project, on the unit titled "Create a Search Index Configuration".
I am completely stuck trying to verify the final step. I successfully created the Search Index Configuration (My_kav), clicked Rebuild, and waited until the Search Index Last Run Status officially changed to Ready.
However, when I click the "Verify step" button on Trailhead, it consistently throws the generic red error:
"Whoops, looks like there was a problem. Please try again."
To investigate further, I went into Data Explorer and selected the chunk table (My_kav_chunk__dlm), but it throws a database execution failure error:
Failed to execute query: table "My_kav_chunk__dlm" does not exist [TraceId: ...] SQLSTATE: 42P01
Here is what I have already tried to fix it:
- Waited 15+ minutes to allow backend provisioning.
- Triggered manual Rebuilds multiple times.
- Deleted the Search Index configuration completely, waited, and recreated it from scratch with the exact configuration required.
- Attempted checking the challenge using a fresh Incognito window to clear any browser cache.
Even though the UI says the index is Ready, the backend DLM tables seem broken or unprovisioned, preventing the Trailhead grader from reading them. Has anyone found a workaround for this backend provisioning delay, or is my playground org's Data Cloud instance glitched?
Any help would be greatly appreciated! Thank you!
#Trailhead Challenges #Data Cloud #Trailhead Challenges
답변 6개
Hi, there may be issue in that org, you can create a new one and do that again.
This happens sometimes in Salesforce playground or dev orgs.
Hello everyone
I am getting this error in this challange :
https://trailhead.salesforce.com/trailblazer-community/topics/trailheadchallenges?sort=LAST_MODIFIED_DATE_DESC&search=Define+Dependencies+and+Fulfillment+Scenarios&ref=unit
Error: In the Laptop Pro Master Orchestration fulfillment workspace, we can’t find the ‘Scenario Laptop Pro Invoicing’ scenario.
Steps to Follow:
- In the Laptop Pro Master Orchestration workspace, click anywhere in the Invoicing fulfillment step group.
- In the side panel that opens, go to the Related tab and in the Scenarios section, click New.
- In the Create Product Fulfillment Scenario window, add these details.
- Name: Scenario Laptop Pro Invoicing
- Action: Add
- Product: Laptop Pro Bundle
- Save your work
Which I have done see below image:
but it is not seeing it, what have I done wrong here?
#Trailhead Challenges
답변 1개
Hey Melanie,
Your setup in the screenshot matches the official steps exactly (Name, Action: Add, Product: Laptop Pro Bundle), so the immediate fields look correct. A few things worth checking given the exact wording of the checker error:
1. Confirm the record actually saved, not just appears in the panel. Go back to the main Laptop Pro Master Orchestration workspace view (close the side panel entirely) and check if "Scenario Laptop Pro Invoicing" shows up in the Scenarios list under Invoicing there, not just inside the panel you had open when creating it.
2. Double-check exact spelling/capitalization, "Scenario Laptop Pro Invoicing" needs to match character-for-character (the checker is typically case- and space-sensitive).
3. Per the official steps, this same pattern (create a scenario per fulfillment step group) needs to be repeated across other lanes too, not just Invoicing. If the challenge checker validates all expected scenarios together and one from another lane is missing or misnamed, it can sometimes surface the error against a different scenario name than the one actually missing. Worth confirming all your lanes (Inventory Management, etc.) have their expected scenarios created too, not just Invoicing.
4. Refresh the page fully after saving, sometimes the panel doesn't reflect a true save until a hard refresh.
Reference:
https://trailhead.salesforce.com/content/learn/modules/complex-order-decomposition-and-orchestration-with-revenue-cloud/define-dependencies-and-fulfillment-scenarios
답변 1개
Hey Gaspar,
That error banner is Trailhead's own generic message for a backend playground provisioning failure, not something wrong with your account or setup. It literally tells you the fix path: refresh and retry after some time, this specific "Models API Playground" type has had recurring provisioning hiccups since it's a newer, more specialized org type than a standard Trailhead Playground.
What to actually do:
- Wait longer than the suggested hour if the first retry fails, this specific playground type has been reported to take longer to provision during high-demand periods
- Try from a different browser or incognito window, just in case a stuck session is compounding the issue
- Click the "Get help" link right in that error banner, that routes to Trailhead's support form specifically for this failure, worth submitting if it persists past a few hours
Since your access window is time-limited once the org does provision, I wouldn't spend much more time troubleshooting on your end, this is squarely a Trailhead backend issue to report and wait out.
Reference:
https://trailhead.salesforce.com/help