#Trailhead456 diskutieren mit

Hi @Aashita Rajput,

The most likely problem is the org. The challenge only works in the Trailhead Playground made for this badge. The link you shared looks like a normal Developer Edition org, so the checker cannot find your template there.

Please try this:

1. Open the “Get Started with Prompt Builder” project on Trailhead.
2. Scroll to the Challenge section and click Launch (or Create Playground).
3. In that org, create the template with these exact values: 
   • Type: Field Generation
   • Name: Quick Summary
   • API Name: Quick_Summary
   • Object: Case, Field: Quick Summary
4. Make sure the template is Activated.
5. Go back to the project page and click Check Challenge.

If it still fails, check that Agentforce Studio is turned on in Setup. Let us know how it goes.

こんにちは。商談の履歴トレンドは次の手順で有効化できます。 

1) 設定のクイック検索で「履歴トレンド」を開き、オブジェクト一覧から「商談」を選択します。 

2) 画面上部の「履歴トレンドの有効化」にチェックを入れます。これが機能自体のオン／オフで、事前準備として必要なのはこのチェックです。 

3) 下の「項目の選択」は、どの項目の変更履歴をトレンドデータとして保存するかを決める設定です。チェックした項目だけが「履歴トレンド」レポートで過去の値と比較できます。特に必要がなければ、初期状態のままで問題ありません。 

4) 保存したら、レコードクローンのインストールを再度試してください。 

履歴トレンドを有効にしても既存のデータやレイアウトは変わらないので、安心して設定して大丈夫です。ご参考になれば幸いです。

@Navarun Halder

, 

Salesforce Support has confirmed that this is a known issue. 

Workaround to complete the challenge

: Creating a new Org again from scratch and repeating the steps fixed the issue.  

To create a new Org using the button "

section. 

This will allow you to

from your Trailhead profile. 

Once the exisiting Playground is disconnected, you will see "

" button on the unit once again, you can use the same to initiate the creation of new Einstein AI Playground and repeat the steps. 

This has worked for me & I was able to complete the badge.

Hi Guilherme, good questions. Building and testing in a sandbox is the right approach for journeys, segments, content and flows, but treat channel setup as per-org configuration rather than something you deploy. 

1. WhatsApp: The WhatsApp sender is tied to a phone number registered with Meta under a WhatsApp Business Account, and a number can only be active in one place at a time. Use a separate test number (or Meta's test setup) in the sandbox for development and testing, and plan to connect the real business number directly in production. You will repeat the channel connection and template approval steps in production, so document them as a go-live runbook. 

2. Email: Sender domain/subdomain authentication (SPF/DKIM records) is configured per org, so you set it up again in production. For the sandbox, use a dedicated test subdomain so test sends never touch your production sending reputation. IP/domain warming only matters where you send real volume, which is production. Sandbox sends are low volume to internal test addresses, so there is nothing to warm there. 

3. What does deploy: segments, journeys/flows, content and data model changes can move through your normal deployment path (change sets, DevOps Center or a CLI pipeline), but check the current Marketing Cloud Next documentation for which components are supported metadata, as coverage has been changing release to release. 

Tip: build a go-live checklist early that lists every manual production step (WhatsApp number connection, template approvals, domain DNS records, consent/compliance settings, warming plan). DNS changes and Meta approvals can take days, so start them in production in parallel with sandbox testing rather than after sign-off.

Same issue here on 10/24/2026. Module: Quick Start: Create a Prompt Builder Flex Template, challenge "Add a Flow to Your Prompt Template".

The checker returns: "We couldn't find the prompt template New Guest Newsletter that is activated."

What I've verified in my Playground:

• The Flex template "New Guest Newsletter" (API name New_Guest_Newsletter) is Active, and it's the only template with that name.
• The Template-Triggered Prompt Flow "Get Experience Newsletter Data" is Activated and inserted in the prompt.
• Preview works and generates the newsletter correctly.
• The Playground username matches the one under Connected Orgs.
• I tried different template versions, deactivating and reactivating, and incognito mode, with the same result.

This looks like the checker issue Salesforce staff acknowledged earlier in this thread. Is there any update or workaround? My Playground expires today at 9:00 PM (GMT-3), so a manual credit or a new Playground would also help.

Thanks!