#Trailhead Challenges1,138 人がディスカッション中

Hi @Aaron Alexander I checked your screenshot. The issue appears to be related to Agentforce Builder compilation, not necessarily your Flow configuration.

I can see two errors:

• "We couldn't compile the script. Try again later."
• "Something went wrong. Refresh and try again."

Please try these steps:

1. Check Script View: Open Agent Script and look for syntax or configuration issues.
2. Review Warnings: Check the 7 warnings shown in the Problems panel.
3. Verify Flow Actions: Confirm the Flows are active and their input/output variables are configured correctly.
4. Check Agent Settings: Make sure the agent and its subagents are configured correctly.
5. Save and Retry: Save the draft, reopen Agentforce Builder, and test again.
6. Try a New Version: If possible, create a new draft version and check whether the issue continues.

Official Salesforce Resources:

• Agentforce Documentation
• Agent Script Documentation
• Trailhead Help

Since refreshing hasn't helped, focus on the compilation error first. If the problem continues with valid configurations, it could be a Salesforce platform-side issue.

You can raise a Trailhead support case with the screenshot and exact error message. 

Hope this helps! Venkat Yadav | SFDCINDIA

Hi @Gibran Waldron I checked your screenshots. The error "We couldn't compile the script. Try again later" appears to be related to Agentforce Builder compilation, rather than the Flow itself.

Please try these steps:

1. Check Agent Script: Open Script View and look for any syntax or configuration issues.
2. Verify Action Inputs: Make sure the Flow action inputs and outputs are mapped correctly, especially the required variables.
3. Check Variables: Review any undefined variables or incorrect data types.
4. Review Warnings: Your screenshots show three deprecated topic warnings. These may need updating, but they aren't necessarily causing the compilation failure.
5. Save and Retry: Save the agent, refresh Agentforce Builder, and try compiling again.
6. Test the Flow Separately: Run the Flow using Flow Debugger to confirm it works independently.

Official Salesforce Resources:

• Agentforce Documentation
• Agent Script Documentation
• Trailhead – Agentforce

My Suggestion:

Since you've already tried a new Developer Org, I would first check the Agent Script and action mappings. If everything looks correct and the error continues, it may be a platform-side compilation issue. 

Hope this helps! Venkat Yadav | SFDCINDIA

Hi Tuan, 

I faced the same issue in the Trailhead challenge “Refine Your Prompt Template for Accurate Agent Replies.” 

My Agentforce preview was working correctly, but Trailhead was still showing:

“Challenge not yet complete. Whoops, looks like there was a problem. Please try again.” 

I fixed it by checking the following steps: 

1. Go to Setup → Flows.
2. Search for Get Open Cases for Contact.
3. Open the flow and make sure it is Active.
4. Go to Setup → Prompt Builder.
5. Open the prompt template Guest Experience Compensation.
6. Make sure you are working on the latest version of the prompt template.
7. In the prompt, after Case Details:, insert: Insert Resource → Flow → Get Open Cases for Contact
8. After Complaint:, insert: Insert Resource → Free Text → Complaint
9. Do not manually type the resource names. Insert them using the Insert Resource option.
10. Save the prompt template.
11. Test it in Preview with Sofia Rodriguez.
12. Confirm that the resolved prompt contains:
    • Contact details
    • Open case details
    • Complaint
    • Compensation instructions
13. Click Activate for the latest version of the Guest Experience Compensation prompt template.
14. Go back to the Coral Cloud Experience Agent.
15. Refresh the agent preview and test again.
16. Use: The White Water Rafting experience my family and I booked was unexpectedly cancelled.
17. When the agent asks for customer details, enter:  I'm sofiarodriguez@example.com and my membership number is 10008155.
18. If the agent response is working correctly, go back to Trailhead and click Check Challenge again.

The main things to verify are: 

Get Open Cases for Contact Flow → Active

Guest Experience Compensation → Latest Version Active

Case Details → Flow resource inserted correctly

Complaint → Free Text resource inserted correctly

Thank You, 

Venkat Yadav.

@Luis Daniel Castañeda Vargas That line isn't a Live Chat outage. It's the fallback when the conversation never reaches an activated agent. Einstein being on doesn't activate the agent.

In that unit the chat is hitting the agent the step is testing. If the agent is still a draft, or you opened a different one, you get exactly this message. The same thing happens when the user in the playground doesn't have the Agentforce access the earlier steps assigned. The panel opens, and there's no agent behind it.

Open the agent from this playground, confirm it's the one the step names, and activate it. Then start a new conversation. The chat you already have is a failed session, and refreshing it keeps the same failure.

Hi @Hanisha A From your screenshots, the Campfire Stories agent is active, but the chat panel is still showing the Data 360 Marketing Agent. 

Try these steps:

1. Check Agent Access: Make sure your user has permission to access the Campfire Stories agent.
2. Check Agent Settings: Verify that the agent is configured for the Employee Agent experience.
3. Agentforce Registry: You don't need to register the agent under APIs or MCP Servers for this.
4. Check Agent Assignment: Verify which agent is configured to appear in the Salesforce chat panel.
5. Refresh and Test: Log out, log back in, and check again.

Important: Activating a custom agent doesn't automatically make it appear in the Salesforce chat panel.

Also, make sure you're using the correct Trailhead playground.

Hope this helps!

SOLVED - and the culprit was neither the connector package nor caching. Posting this in case it helps the next person. 

The real cause was two toggles in the Quick Start that I had skipped: 

Setup > Quick Find > Einstein Bots  ->  was OFF, I turned it On 

Setup > Salesforce Go > Search features > Agentforce (Default)  ->  was OFF (still showing Get Started), I did Get Started > Turn On > Confirm 

The Quick Start lists THREE toggles in its "Activate Einstein, Einstein Bots, and Agentforce" section - Einstein Setup, Einstein Bots, and Agentforce (Default). I had only done Einstein and Agentforce Studio. Once both were On, the checker message changed immediately from "...not prepared for agent deployment into Slack" to just the generic "Whoops" message, and after that unit 2 passed. 

Important note: a brand-new org from the agentforce-for-slack-on-trailhead promo does NOT come with Agentforce (Default) already enabled. You have to run that toggle yourself. Einstein Bots is easy to overlook because nothing else in the module mentions it. 

For anyone stuck on unit 3 (Deploy an Agent in Slack), the checker message is very specific: "We can't find the conversation with the Product Management Agent agent. Make sure the messages show up on the Slackbot direct messages." 

Gotcha: a chat with Slackbot does NOT count. You must open the Agentforce Hub / Tools > Agents, open Product Management Agent itself, and start the conversation there. Also give the agent concrete details, otherwise it just replies with clarifying questions and never logs a gap or creates a canvas. A prompt that worked: "Log a product gap: our current product lineup has no analytics or reporting coverage for the new business unit. Contact is Sofia Rodriguez,

. Please create a canvas called Product Gaps with these details." 

Thanks again Vishal - your reply sent me to Installed Packages, and chasing that is what made me re-read the Quick Start and notice the two toggles I had skipped.

Hi @Charlie Parfet

I can understand how frustrating this is, especially after trying the same challenge multiple times.

From your screenshot, the Coral Cloud org and Guest Agent look okay. I would check a few things before trying again:

• Open reservation R-00000017 and confirm its current status.
• Make sure the Cancel Reservation action or Flow is active.
• Confirm that action is added to the correct subagent.
• Test the cancellation in Agentforce Builder and make sure the reservation record is actually updated.
• Avoid deleting and recreating the reservation unless the challenge specifically asks you to.
• Also make sure Trailhead is checking the correct special Developer Edition org.

If everything is working correctly but the challenge still does not pass, then it could be a Trailhead validation issue. 

Since you have already been trying for weeks, I would suggest raising a Trailhead Help case with the screenshot, challenge name, reservation number, and the exact error message.

Hope this helps. 

Thank you, 

Venkat Yadav.