Feed

Hi , 

I encountered the same issue where the option “SFDX: Turn On Apex Debug Log for Replay Debugger” didn’t appear in the Command Palette. I later found out that this command was removed in newer versions of the Salesforce VS Code extensions. The Replay Debugger now relies on existing debug logs in your org instead of enabling logging from VS Code. 

To generate logs, you need to enable debug logging in Salesforce Setup: 

Setup → Debug Logs → User Trace Flags → New. 

After that, you can continue with the next steps in VS Code.  

https://trailhead.salesforce.com/trailblazer-community/feed/0D54V00007TsugHSAR 

Hi , 

Just as a follow up to my above issue, I figured out it was the Salesforce license type I was choosing. For both users I chose 'Salesforce Platform; while that is correct for Suzuki Fumiko - Aaron Hartzler should be User License: Salesforce.  

For anyone who has confirmed they’re in the correct org but still can’t find the Coral Cloud Booking Agent, here’s a workaround that let me continue without starting over, using Agentforce’s ability to share agents via script: 

1. Create a new org using this link: https://trailhead.salesforce.com/promo/orgs/agent-customization-with-agentforce-flows (you’ll only use it to copy the agent).
2. Check that the Coral Cloud Booking Agent exists in the new org. If it doesn’t, try creating another org or contact Trailhead Help.
3. Open the agent and switch from Canvas to Script view.
4. Copy the entire script and save it somewhere temporarily.
5. In your original org (where you completed the previous units), go to App Launcher > Agentforce Studio, click the dropdown arrow next to New Agent, select New from Script, and paste the script.
6. Click Create Agent. Note: the script still points to the other org’s agent user (default_agent_user), so you need to reassign it before saving.
7. In Setup, go to Users and open EinsteinServiceAgent User. Confirm the User License is Einstein Agent.
8. If the Profile is Custom Einstein Agent User and the user doesn’t show up in the next step, edit the user and change the Profile to Einstein Agent User. (Heads-up: the custom profile may include extra permissions. If your agent’s actions fail with access errors later, switch it back.)
9. Go back to Agentforce Studio, open the Coral Cloud Booking Agent, and click Save. When the Select User window appears, choose EinsteinServiceAgent User.
10. Continue with the unit as usual and run Check Challenge.

This worked for me and passed validation without redoing the previous units. Hope it helps!

Your trigger is most likely firing fine. The catch is the Upload Files dialog on the related list doesn't show the text from addError on ContentVersion, it just replaces it with its own generic "Can't upload" message. You can confirm by turning on a debug log for your user and uploading a file with a long name, your message should show up in the log. 

If blocking isn't a hard requirement, an easier route is to shorten the name in the same before insert instead of throwing an error, so the upload just goes through:

if (file.Title != null && file.Title.length() > MAX_CHAR_LIMIT) { 

    file.Title = file.Title.left(MAX_CHAR_LIMIT); 

} 

Title doesn't include the extension (that's on PathOnClient / FileExtension), so the file still opens normally. If you do need to block it, it's probably worth adding a note near the related list so users know about the 80 character limit, since they won't see your custom text.