Skip to main content
Rachel Negron (Tableau) 님이 #Trailhead Challenges에 질문했습니다

I keep hitting this error. below is the prompt I put in for  Coral Cloud FAQ Answer From Document prompt template followed by the error... what am I missing? and yes its active.  

 

You are a guest-services assistant for Coral Cloud Resorts. 

Answer the guest's question using ONLY the information contained in the 

attached document. Do not use any outside knowledge or make assumptions. 

Strict rules: 

- Base your answer solely on the attached document. 

- If the answer is not present in the document, respond exactly with: 

 "I'm sorry, I don't have that information. Please contact the Coral Cloud 

 front desk or concierge for help." 

- Do not mention "the document," "the file," or "the PDF" in your answer — 

 just answer the guest naturally. 

- Keep the answer concise and friendly. 

Guest question: {{Input.question}} 

 

Challenge not yet complete in

redo@redo.com

The prompt template ‘Coral Cloud FAQ Answer From Document’ is missing required prompt text, resource input, or has not been activated. Ensure that you updated the template with the prompt scenario text, then saved and activated the version. Review Help article section 'Improve FAQ Prompt Templates' for guidance. 

 

#Trailhead Challenges

답변 1개
  1. 10월 22일 오후 6:50

    Hi! I ran into this exact same issue, and it turns out to be a hidden bug with how Salesforce recently updated the Prompt Builder syntax versus how the Trailhead grader checks your work.

    Here is what is happening under the hood and how to fix it:

    The Problem

    • Old Syntax: Trailhead's grading logic expects the prompt template to use the old Salesforce merge field format: {!$Input:Question}.
    • New Syntax: The latest version of Prompt Builder automatically formats this resource as {{Input.Question}}.

    Because the Trailhead grader is specifically hunting for the old {!$Input:Question} text, it thinks the resource is missing entirely and throws that error. Trying to type it manually in the UI doesn't work because Salesforce auto-converts it back to the new syntax upon saving. 

    Hence, there is no direct fix available