Feed

Hi, @Melissa Ngamini

Try entering text or part of a word first, then select a value from the dropdown list, so that in the end you have a result similar to this: Final result:

Accordingly, perform similar actions in other elements as specified in the instructions. 

Sincerely, 

Mykhailo Vdovychenko 

Bringing Cloud Excellence with IBVCLOUD OÜ

PS.  You also want to make sure the Report is filtered to only display Closed Opportunities, because they have reached their conclusion.  Including Open Opportunities would skew the results, as open opportunities have not yet reached their final status as Won or Lost  

Hello @Nick Maio, 

Thank you so much to your answer, but, my scenario doen't involves an omniscript, it's a scenario only executed in a Integration Procedure! 

The Integration Procedure will be called by an Apex REST API and specific scenario i need to update an object field using an Post DataMapper inside with a actual DataTime Value substracting 1 hour. 

Leonardo Miranda.

If anyone else runs into this error - I somehow was able to create six checkpoints in dev console. When I removed one, I no longer got this error and was able to save again.

Here are the most common reasons you’ll see a failure when you click Get Einstein Recommendations, and exactly how to fix each one:

1. You’re testing on the wrong record page 
   Einstein Work Summaries for Service only runs in a
   Messaging Session record—not on the Case record itself.
   • In your Service Console, click the App Launcher → Messaging Sessions → open any session.
   • Make sure you’ve linked that session to a Case in the Case Summary component.
   • Only then will the Get Einstein Recommendations button become active—and the AI will actually run.
2. Your field mappings aren’t saved or active 
   The component needs to know which Case fields to write into.
   • Go to Setup → Einstein Work Summaries → Enhanced Messaging tab.
   • Click Edit, map Summary, Issue, Resolution to the Case fields you created, and Save.
   • Then toggle Messaging Session Summaries to Active. Trailhead
3. You haven’t added the Einstein Field Recommendations component correctly
   • In Setup → Lightning App Builder, edit your Messaging Session page.
   • Drag Einstein Field Recommendations under your “Service Replies” header.
   • In its properties:
     • Header: e.g. Case Summary
     • Recommendation Type: Wrap‑Up
     • Lookup Field: Use This Messaging Session
     • Update Action: your Generative AI Summarization quick action
   • Save & Activate that page.
4. No conversation data or unsupported channel 
   If the session has no chat transcripts (or isn’t on a supported channel—Messaging, Chat, Voice), Einstein has nothing to summarize and may error out.
   • Send at least a few messages through your chat channel, then refresh your Messaging Session record before clicking Get Einstein Recommendations.
5. Missing permissions or licensing 
   You need the
   Einstein for Service license and the Einstein Work Summaries User permission set.
   • In Setup → Users, open your user record.
   • Under Permission Set Assignments, make sure Einstein Work Summaries User (or the “Salesforce Einstein” bundle) is assigned.
   • If you’re on a Trailhead Playground that doesn’t include those licenses, switch to a proper Developer Edition org created via the module’s Launch link—Playgrounds don’t all support Einstein.
6. Inspect the status console or debug logs
   • Go to Setup → Einstein Recommendations → Implementation Status. Fix any red‑flag errors listed there. Salesforce
   • Or turn on a debug log for your user (Setup → Debug Logs → New), rerun Get Einstein Recommendations, then inspect the log for the precise exception.

1. Turn on a debug log for your user

1. In Setup, search Debug Logs and open it.
2. Click New, choose your user, and save.

2. Re‑run Check Challenge

• Back in Trailhead, click Check Challenge again.
• This will trigger the failing insert and record it in your debug logs.

3. Inspect the log for the root cause

1. Return to Setup → Debug Logs, refresh the list, and open the newest entry.
2. Search (Ctrl+F) for System.DmlException or EXCEPTION_THROWN.
3. Just above that you’ll see what rule/trigger/flow fired and why.
   • Validation Rule: you’ll see the rule name and formula.
   • Apex Trigger/Flow: you’ll see the trigger or flow name and the error message.
4. Note exactly which metadata item is throwing the error.

4. Fix or scope your validation rule (if that’s it)

If your own rule is blocking the insert, scope it so it only fires when you want—for example, only on updates:

sqlCopyEditAND(
  NOT(ISNEW()),
  /* your original criteria, e.g. Discount_Percent__c < 0 */
)

Deactivate any other validation rules on Opportunity that aren’t part of this challenge.

• Make sure your rule’s API Name matches what Trailhead expects.

5. Check for other blockers

• Required custom fields: In Object Manager → Opportunity → Fields, ensure no custom field is marked “Required.”
• Triggers/Flows/Process Builders: In Setup, search Apex Triggers and Flows, and temporarily deactivate anything acting on Opportunity.

6. Retry the challenge

Once you’ve corrected the offending rule/trigger/flow:

1. Clear your debug logs (optional) so you can see the next run cleanly.
2. Go back to Trailhead and Check Challenge again.

Hi @Kimberly Cobb aka "Kimpossible"

- Please check the below steps 

• Click your browser’s Reload button (or press Ctrl + R / Cmd + R).
• If the “Authorize access…” button reappears, click it and complete the Slack OAuth flow.

Use an incognito/private window

• Often a stale cookie or extension (ad‑blocker, privacy guard) will block the OAuth callback.
• Open a fresh private session, log into Trailhead, and launch the Playground again.

Disable pop‑up blockers and CORS blockers

• Make sure your browser isn’t preventing the Slack auth window.
• Temporarily turn off extensions like uBlock Origin, Ghostery, or any strict firewall rules.

Confirm your Slack permissions

• You must be able to create/install apps in the Slack workspace the Playground spins up.
• If you’re using a corporate-managed Slack, ask an admin to grant you the “Install Apps” permission or use a personal workspace for Trailhead.

Disconnect and recreate the Playground

• In Trailhead, click your avatar → Hands‑On Orgs.
• Under Slack Playgrounds, find the one with the error and click Disconnect.
• Return to the module and click Launch or Create Playground again — this forces a fresh provisioning.

Try a different browser or network

• Sometimes corporate VPNs or proxies interfere.
• Switch to Chrome if you’re on Firefox (or vice versa), or move off VPN/Wi‑Fi to see if it succeeds.

Wait and retry later

• Occasionally the provisioning service is under load.
• If it’s a backend hiccup, give it 10–15 minutes and then try again.

That “unexpected error…while inserting Opportunity records” almost always means one of two things in your org is blocking every new Opportunity:

1. A validation rule that’s firing on insert, and
2. A required field (standard or custom) that isn’t being populated by the Trailhead checker.

To get past it, you’ll need to adjust your Opportunity setup so that Trailhead’s automated insert can succeed. Here’s exactly how:

1. Audit your Opportunity Validation Rules

1. Go to Setup → Object Manager → Opportunity → Validation Rules.
2. Deactivate all custom rules except the one you wrote for this challenge.
   • Click the rule name → uncheck Active → Save.
3. Rerun the Trailhead check.
   • If it now passes, one of the other rules was blocking the insert.
   • Reactivate your challenge rule and leave the others deactivated for now.

2. Verify Required Fields

Salesforce requires certain standard fields on Opportunities—Opportunity Name, StageName, CloseDate, and Amount—and any custom field you’ve marked “Required.” If any of these are truly required at the field‑definition level, the checker’s insert (which doesn’t supply them) will fail.

1. In Setup → Object Manager → Opportunity → Fields & Relationships, sort by Required.
2. For any custom field you don’t absolutely need “Required” on, click it → Edit → uncheck Required → Save.
3. Leave standard fields alone; Trailhead’s checker will populate the standard ones for you.

3. Check Your Page Layouts & Default Values (Optional)

Although page layouts don’t block API inserts, if you added default value formulas that reference missing data, they can fail on insert.

• Open any custom default‑value formula and make sure it doesn’t BLANKVALUE() to a field that doesn’t exist.
• If you’re unsure, remove or simplify the default value.

4. Retry the Challenge

1. Go back to your Trailhead module.
2. Make sure only your intended validation rule is active and no extra fields are “Required.”
3. Click Check Challenge again.

You won’t get a “Resend password” link from inside the challenge itself, but you can quickly reset your Agent Service Playground password two ways:

1. From Trailhead’s Hands‑On Orgs page

1. In Trailhead, click your avatar (top right) → Hands‑On Orgs.
2. Find the entry for your Agentforce for Service Playground (it may be called “My Playground” or similar).
3. Click the dropdown arrow at the end of that row and choose Reset My Playground (or Reset Password).
4. Confirm — Trailhead will rebuild the org and email you a fresh set of credentials.
5. Check the inbox (and spam/junk) of the e‑mail you use for Trailhead; you’ll get a new username/password and a link to log in.

2. Via the standard Salesforce “Forgot Password” flow

1. Copy the Username for that Playground from the Hands‑On Orgs page.
2. Go to your Playground’s login URL (it’ll look like https://<something>.my.salesforce.com).
3. Click Forgot Your Password?
4. Enter that Playground username and your Trailhead‑registered e‑mail.
5. You’ll receive a password‑reset e‑mail; follow the link to set a new password.