Admin Group, Jaipur, IN

I ran into this exact error when I did that module, and it turned out to be something small. A couple of things to double-check:

1. Component name vs. label
   • The Trailhead checker is looking for the component label to be exactly Recent Items (not “Recent Cases”).
   • You can still point it at the Case object, but the label has to stay as “Recent Items” for the badge to validate.
2. Number of records
   • Make sure it’s set to 5 (sounds like you already did that).
3. Save + Activate
   • You mentioned activating — just confirm you assigned the Lightning Home page as the org default for the app you’re in (sometimes it’s only activated for one app, and Trailhead is checking another).
4. Caching
   • If all looks correct, try logging out / logging back in, or refreshing the playground. The Trailhead checker can be a little picky.

So the main thing: switch the label back to Recent Items and try verifying again. That usually clears the error.

Hi @Divya Chauhan

Thank you so much for sharing these helpful links! The resources have given me a lot of clarity about Salesforce career options and opportunities for people from diverse backgrounds. It's reassuring to know that with dedication and certifications, I can overcome challenges like my non-IT background and career gap.

Since you seem experienced, could you please guide me on how to network better or approach companies when I complete my Salesforce Admin and Developer certifications? 

This error occurs when you try to access or update a record that you don't have the necessary permissions for. Here are the possible reasons and solutions

:

Reasons:-

Missing Sharing Access:

You don't have access to the record due to sharing rules or manual sharing.

Field or Object Permissions:

Your profile or permission set lacks the required Read, Edit, or Delete permissions for the object or field.

Incorrect Record Ownership:

The record is owned by someone in a restricted role hierarchy.

Invalid ID:

The referenced ID might be incorrect or belongs to a different org.

Solutions:

Check Sharing Settings:

Ensure you have appropriate sharing access to the record.

Verify Profile/Permission Sets:

Confirm your profile has the necessary permissions on the object and fields.

Review Role Hierarchies:

Check if the role hierarchy provides sufficient access to the record owner.

Validate the ID:

Ensure the ID is correct and exists in the current org.