Feed

can you share the screen shot for the task that you Performed so it will help to identify the issue.

can you share the screen shot ?

I’d double-check two things: you're trying to reset the password for the correct org, it's different from your main Trailhead or sandbox logins. Second, check your spam/junk folder, those reset emails sometimes land there. If nothing’s coming through at all, I’d suggest spinning up a fresh org from the trail link again.  

Just use a different email alias (like [name+ai@domain.com](mailto:name+ai@domain.com)) to avoid conflicts. That usually works when the original setup hits a weird state.

Yeah, most survey tools lean toward Sales/Service Cloud. If you're set on syncing responses into Account Engagement, you might need a third-party tool, like Skyvia. It can move survey data into custom fields or objects tied to prospects

Hi @LAUREN JONES

You can reach out to Expert Coaching Individual Session to get inputs on above scenario if you have Premier or Signature Success Plans.  

Thanks!

Hi @Rohit Heera

Check below reference that can help you. 

Thanks!

There’s no native app for full bidirectional sync between Freshservice and Salesforce, but you can set it up using integration platforms, like Skyvia. They help with cases where you want to map data both ways without heavy coding. (https://skyvia.com/data-integration/integrate-freshservice-salesforce)

If it helps anyone, I have passed the challenge. While updating the single sign on settings I selected the wrong Signature method. Instead of selecting RSA- SHA1, I had selected RSA-SHA256. So do check that once for those who have done everything correctly and passed the SAML response but still getting We can't find the expected SAML Single Sign-On settings error.

The Fitness custom object isn’t included by default in a regular developer org, it’s specific to the special org provisioned for the Prompt Builder Superbadge. You’ll need to sign up using the dedicated link provided in the superbadge instructions (usually labeled Get Your Special Org). If you already did that but still can’t see the object, double-check you’re logged into the correct org, users often accidentally switch to a standard dev org without realizing it. If the issue persists, you might need to request a fresh org through the same link and start from there.