#Trailhead Challenges1,150 discussing

@Eljesa Bajrami , Go to your Agentforce Org Setup.

Search for Installed Packages in the Quick Find box.

Verify that the Slack Platform Connector is present.

If it is missing or failing, search for Connected Apps OAuth Usage in Setup, find the Slack app, and make sure Slack OAuth is enabled with explicit user access allowed.  

Also , Verify Your Active Workspace Connection status

The challenge checker requires your specific Trailhead playground domain to be actively mapped inside your target Slack environment. 

1. Log into your Slack workspace or Enterprise org used for the quick start.
2. Click your workspace name > Tools & settings > Organization settings (or Administration).
3. Look for the Salesforce | Agentforce tab.
4. Check if the connection request to your specific Salesforce My Domain URL is Approved and Activated. If it shows as pending, click Review and allow it access to your workspace

If both steps look right but the error won't go away, the automated checker is likely stuck on cached org tracking metadata:> Disconnect and reconnect: Go to the bottom of the Trailhead challenge page, switch your selected hands-on org to any other playground, wait 10 seconds, then switch it back to your Agentforce Developer Edition org before hitting check again

Hi @Pranay yerragunta If a user can access the record but cannot see a particular field, I would troubleshoot it in this order:

1. Field-Level Security (FLS): Check whether the field has Read access through the user's Profile or Permission Sets.
2. Page Layout: Verify that the field is added to the page layout assigned to the user.
3. Lightning Record Page: If Dynamic Forms are used, check whether the field is added and whether visibility filters are hiding it.
4. Permission Sets: Check the user's assigned Permission Sets and Permission Set Groups for field access.
5. Record Type: Verify that the correct page layout is assigned based on the user's Profile and Record Type.
6. Login as User: Test using the affected user's access to identify where the field is missing.

Important: Record access, object permissions, and field-level security are different. Having access to a record doesn't automatically provide access to every field.

Best Practice: Start with Field-Level Security, then check the Page Layout and Lightning Record Page. These are common reasons for field visibility issues.

Hi @Rohith thammali When working with thousands of records in Apex, writing efficient SOQL queries is very important to avoid governor limits.

A few best practices I follow:

1. Avoid SOQL inside loops. Query records once and process them using collections.
2. Fetch only required fields. Avoid unnecessary fields and records.
3. Use WHERE conditions to filter records efficiently, preferably using indexed fields.
4. Use Maps and Sets to handle bulk records and avoid repeated queries.
5. Use Batch Apex when processing large data volumes.
6. Use LIMIT carefully. It's useful when you need only a specific number of records, not when you must process everything.

Also, remember that synchronous Apex generally allows 100 SOQL queries and 50,000 queried rows per transaction.

Focus on bulkification, selective queries, and proper collection usage. These make a big difference in real-time projects.

Hope this helps!

Hi @Rohith thammali To handle 200 records efficiently, I would focus on bulkifying the Apex Trigger.

A few best practices I follow:

1. Avoid SOQL and DML inside loops to prevent governor limit errors.
2. Use Trigger.new to process all records together instead of one by one.
3. Use Sets and Maps to collect record IDs and retrieve related data efficiently.
4. Perform bulk DML operations using a List instead of updating records individually.
5. Use a Trigger Handler Class to keep the logic organized and maintainable.
6. Test with 200 records to verify bulk processing and governor limit usage.

Always design a Trigger to handle multiple records, even if the requirement initially involves only one record.

This approach improves performance and makes the code more scalable and easier to maintain.

Hope this helps!

Hi @Abhiram Sailada You can achieve this easily using an After-Save Record-Triggered Flow.

1. Go to Setup → Flows → New Flow → Record-Triggered Flow.
2. Select Opportunity as the object.
3. Set the condition: Stage = Closed Won.
4. Choose When a record is updated and Only when the record is updated to meet the condition requirements.
5. Select After Save because we're creating a related Task.
6. Add a Create Records element to create a Task with:
   • Subject: Follow up with Customer
   • Status: Not Started
   • Related To: Opportunity ID ($Record.Id)
   • Assigned To: Opportunity Owner ($Record.OwnerId)

Finally, save, activate, and test the Flow.

Best Practice: Make sure the Flow creates the Task only when the Opportunity changes to Closed Won, to avoid duplicate Tasks.

Hope this helps!