#Agentforce토론 중인 항목 309개

Hi @Saisri Gajula and @Andreea Ionescu

1. Connected org. The checker only inspects the org connected to your Trailhead account. In the Verify Step section at the bottom of the unit, click your Playground name and check that it says it's connected. If you built the template in a different org (a Developer Edition or an older Playground), the checker will never see it. The unit says to connect the org first, so the "Connect Org" step is easy to skip.
2. Same Playground for prerequisites. The unit expects Einstein for Sales to be enabled and the Guest Events tab to exist. The Guest Event object comes from the earlier steps in this path. If you're in a fresh Playground that skipped them, the template can look right but fail validation.
3. Exact template settings.
   • Type: Sales Email
   • Name: Welcome Guest
   • API name: Welcome_Guest
   • Related Object: Guest Event
4. Activation. The error says "active". In Prompt Builder, open the template and make sure a version is Activated, not just saved. A saved draft isn't enough.
5. Prompt body. The unit expects the sender name, phone and email merge fields, plus the check-in welcome instructions, saved in the version you activate.

Practical options if all of that checks out

• Check the expiry. Your screenshot shows the Playground expiring 8 Oct 2026, 5:30 AM IST, which is about two days away. If the checker still fails after you've confirmed the points above, request a new Playground and redo the earlier steps in that one. Creating the template again in a new Playground has worked for some people.
• Open a Trailhead Help case. If it still fails on a clean Playground, report it to Trailhead Help with the screenshot and your Playground details. A validation bug can't be fixed from your side. Replying in the community thread to say you hit the same error also helps surface it.

 I hope you find the above information helpful. If it does, please mark it as Best Answer to help others too.

The challenge only looks in the org connected to this unit, and it looks for an active Autolaunched flow whose API name is exactly Get_Contact_s_Upcoming_Bookings. A matching label is not enough. 1. On the challenge page, confirm the connected playground is the org where you built the flow. If you built it somewhere else, connect that org and check again. 2. In Flow Builder, open the flow properties and confirm the API name is Get_Contact_s_Upcoming_Bookings, with that exact spelling. A special apostrophe in the label often saves a different API name. 3. Confirm the flow type is Autolaunched Flow, not a screen flow or a record-triggered flow. The check ignores other types even when the API name matches. 4. Save and activate that version, then run Check Challenge again. If it still fails, reply with a screenshot of the flow properties showing the type, API name, and status.

The Email Response User permission is required, but it does not turn the button on by itself. Draft with AI shows inside the email composer only after Service Replies for Email is enabled and the user can ground a draft in Knowledge. 1. In Setup, open Einstein Setup and confirm Einstein is turned on. 2. In Setup, open Service Replies. Turn on Service Replies and enable the Email channel. Assigning the permission set does not enable the feature. 3. Confirm Knowledge is enabled and this user can read articles. Service email drafts are grounded in Knowledge, and the button stays hidden when that access is missing. 4. On the case, use the standard Email action and look in the composer toolbar. The button is not on the case page itself. A custom email quick action or the legacy composer will not show it. 5. Confirm the user has the Einstein generative AI permission set license in addition to Email Response User, then refresh Lightning. If those are already in place, reply with whether Knowledge is enabled and whether you are using the standard Email action or a custom one.

Activating the agent does not by itself add the Agentforce icon. The sparkle in the Lightning header is the Agentforce panel, and it appears only when your user can open an active employee-facing connection. 1. Confirm this is an employee agent, or the default Agentforce agent. A service agent connected only to Messaging, Enhanced Chat, or an Experience Cloud site shows up in that channel, not as an icon on the internal home page. 2. In Agentforce Builder, open the agent and check Connections. Add and activate the connection for the Agentforce panel in Lightning Experience. An Active agent status does not create that connection for you. 3. Assign yourself the permission set that connection creates. If your org uses an Agentforce permission set license, make sure that license is on your user as well. 4. The icon lives in the global header, not as a component on the Home page layout. After the permission set is assigned, refresh Lightning or log in again. If the connection and permission set are already in place and the icon is still missing, reply with the agent type and which connections are active.

Hi Aniket, 

Worth reconsidering the fix itself before fighting the DeveloperEdition restriction: per Salesforce's own official Contact DLO-to-DMO mapping reference,

is the standard, correct mapping — that's exactly what you already have. Switching it to "Individual ID → Individual Id" isn't the documented fix; you may be chasing the wrong field. 

The warning text itself is the clue: "Map all required fields to create your unified profiles" — that's a field-completeness warning, not necessarily a primary-key mismatch. Go into the Contact_Home mapping (Data Model → Individual DMO → Manage/Edit mapping for Contact_Home) and check whether other required fields besides the ID (typically First Name, Last Name) are actually mapped, not just the primary key. That's the far more common cause of this exact warning — an incomplete field mapping, not a wrong ID field. 

On the "Switch Mapping is not supported on DeveloperEdition" error: that's a real, known platform restriction — changing which field/DMO a DLO is mapped to after initial mapping is a reconfiguration action that Data Cloud restricts on free Developer Edition trial orgs. Since that path is blocked by design, not by something you're doing wrong, it's not something to work around — it's confirmation you were on the wrong track trying to switch it in the first place. 

So: leave Contact ID → Individual ID as is (it's correct), and instead fill in whatever other required fields are unmapped on that same Contact_Home → Individual mapping. Re-run the Identity Resolution ruleset after that, and the warning should clear without needing the switch at all.

Hi, 

Salesforce's official "Manage Employee Agent Access" doc lists the base requirement as Manage AI Agents OR Customize Application — not strictly requiring Manage Agentforce Employee Agents everywhere. That second permission does exist and is explicitly required for some cloud-specific agent features (e.g., it's named for Consumer Goods Cloud), suggesting it's rolling out product-by-product rather than being universal yet — consistent with it not showing up in a Financial Services Cloud trial org. 

Worth trying: confirm Customize Application is assigned (e.g., via System Administrator profile) and retry activation — per the official doc, that alone should satisfy the base requirement regardless of whether Manage Agentforce Employee Agents exists in your org yet. If it still fails with Customize Application present, that's strong confirmation this is an entitlement/provisioning gap specific to Financial Advisor Assistance in trial orgs — worth a support case to confirm AgentforceEmployeeAgentAddOn provisioning status.

Hi @Mohit Kumar Garg

The Sales Email template type is gated by a separate toggle, a license, and a permission set. I haven't checked your org, so these are in rough order of likelihood.  

1. Sales Emails toggle. In Setup, go to Einstein for Sales and set Turn on Sales Emails to True. This is separate from enabling Einstein generative AI as a whole. A Trailhead user in the same situation saw only Field Generation, Flex, and Record Summary until this was addressed. Their reply thread suggests the toggle was the first thing to check. salesforce salesforce
2. License. Salesforce's help docs say the feature is available with the Einstein for Sales add-on, which is available for an extra cost in Performance and Unlimited Editions. A Trailhead module also lists the Einstein for Sales, Einstein for Platform, or Einstein for Service add-on as sufficient. These sources differ, so check which add-ons your org holds under Company Information > Feature Licenses or Permission Set Licenses. Another Salesforce help page says that to work with Sales Email templates you also need EinsteinGPTSalesAddOn and EinsteinGPTSalesAccessAddOn. If those are missing, the toggle may not appear or the type won't show. Create a Sales Email Prompt Template +2
3. Permission sets. The docs say users who draft emails need the Einstein Sales Emails permission set. For building templates, the person in Prompt Builder also needs Prompt Template Manager. Without these, the option can be missing or the Prompt Builder menu itself can be hidden. salesforcesalesforce
4. Org type. Dev Edition and trial orgs often lack the add-ons, so the type never appears even with everything toggled on. Check which kind of org you're in.
5. Release/UI changes. Salesforce has been renaming and reorganizing Einstein and Agentforce features. If Setup labels don't match, search Setup for "Sales Emails" or "Einstein for Sales" instead of browsing menus.

If everything above is in place and it still doesn't appear, check Setup > Einstein Setup to confirm generative AI is on in the org you're actually logged into (sandbox and production are configured separately). Then raise a Salesforce Support case, since an entitlement may not have provisioned. 

 I hope you find the above information helpful. If it does, please mark it as Best Answer to help others too.

Hi @Dhwani V Ajmera

This generic “Whoops, looks like there was a problem” message in Superbadges usually means the challenge checker is not finding one of the required Flow elements exactly as expected.

For Create Equipment Malfunction Cases, I would recheck these areas:

1. Make sure you are working in the correct Superbadge org, not another Trailhead Playground.
2. Verify the Flow type, Flow name, and API name exactly match the challenge instructions.
3. Check all required objects, fields, conditions, assignments, and Create Records elements.
4. Make sure the Flow is saved and activated.
5. Confirm you didn’t add extra conditions or change any required API names.
6. Run Debug with the expected test data and confirm the case is actually created correctly.
7. If everything is correct, log out/in, refresh Trailhead, and try the challenge checker again after a few minutes.

For Superbadges, even a small mismatch in a resource/API name or condition can cause this generic error.

If possible, share a screenshot of the Flow elements/configuration. That will make it easier to identify exactly what the checker is missing. 

Thank you, 

Venkat Yadav.