I am completing the “Protect Your Data in Salesforce” project, specifically the “Create Sharing Rules” step.
I created the VPs Public Group with these four roles:
- VP of Services
- VP, International Sales
- VP, Marketing
- VP, North American Sales
The group Label is “VPs”, Group Name is “VPs”, and “Grant Access Using Hierarchies” is enabled. The four roles are also correctly created under CEO in the role hierarchy.
However, when I verify the challenge, Trailhead still says: “We can't find members in the VPs Group. Make sure you've included all the VPs in the list.”
I have verified that the required roles are selected in the VPs group. Could you please help me resolve the challenge verification issue?
#Trailhead Challenges
Hi Akshath (and Krishna, since you're in the same spot),
The official unit instructions confirm the steps already given in this thread are correct: "Select all the VPs in the list and click the Add arrow to add them to the Selected Members list," using Roles (not Roles and Subordinates).
Reference:
https://trailhead.salesforce.com/content/learn/projects/protect-your-data-in-salesforce/create-opportunity-sharing-rulesSince you've both already verified Roles-only membership and correct naming and it's still failing, here's what to check beyond what's already been covered:
1. Role hierarchy depth: confirm all four VP roles report DIRECTLY to CEO, not nested under an intermediate role (e.g., under a "VP Team" parent role). If any VP role sits one level deeper than CEO's direct reports, the checker can fail even though it looks correct in the hierarchy view.
2. Group Name (API name) exact match: check Setup > Public Groups > click into VPs > confirm the Group Name field (not just the Label) is exactly "VPs" with no trailing space or different casing, this field is separate from the Label and easy to overlook.
3. Extra/leftover roles in the group: confirm there are exactly the four required roles and nothing else accidentally included (e.g., a duplicate role created during troubleshooting attempts), extra unexpected members can also fail the checker's exact-match validation.
4. Asynchronous recalculation: after saving the group, wait a minute or two before rerunning Check Challenge, group membership changes can take a short time to propagate before the checker query reflects them.
Given both of you have done the documented steps correctly and it's still failing, the most consistently reported fix at that point is a fresh Trailhead Playground, this project's challenge checker has known reliability issues with certain playgrounds, and redoing it in a new one is what resolved it for others hitting this exact same error previously (as Usman noted). If a fresh playground still fails after redoing the exact same correct steps, that confirms it's a checker-side bug worth reporting via "Get Help" > "Report an Issue" on the module page.
