#Trailhead Challenges1.147 utenti parlano di questo argomento

Hi @Kalpana Soram

This usually happens when the project is opened in a normal Developer Edition or regular Trailhead Playground. 

For Connect Flows to Agentforce with Actions, Salesforce requires the special Agentforce-enabled Developer Edition org provided in that project. That org already contains the sample Orders and the Initiate Return 

 Flow needed for the exercise. 

Please try this:

• Open the Connect Flows to Agentforce with Actions project.
• Go to the Sign Up for a Special Developer Edition Org section.
• Create the org using that specific signup link.
• Connect that org to Trailhead.
• Launch the project again from the unit.
• Go to Orders → All Orders and check the records.

There have been similar reports where Orders were empty because the wrong org was being used.

If you are already using the special Developer Edition and still see no Orders, I would suggest creating a fresh special org from the project link rather than creating a normal Playground. 

Hope this helps. 

Thank you, 

Venkat Yadav.

@Giovanni Pedrazzoli connecting the playground on Trailhead does not log that org into the tab where Install runs. Not found means the install link opened in a session that cannot see that package. It is usually a different org than the one the unit created.

In Hands-On Orgs, disconnect the stale ones. Launch the playground from the unit so that tab is that org, then use the unit install link in that same tab. Do not paste the package URL into production or into an older playground.

A package id that 404s is the wrong org. The package is still on AgentExchange. The checker only looks at the org the unit launched.

@Radha Shankar Page does not exist on that step means the playground link is dead, or Agent Builder isn't available in the org the challenge still has connected. Retrying the same URL won't bring it back.

Disconnect it from the challenge's org picker, not from inside the org. If that control isn't there, open your Trailhead hands-on orgs and drop that playground. Then launch a new one from the unit and create the Lead Nurturing agent in Agentforce Studio in that new org. The screenshots in the unit can lag behind the playground UI, so follow the labels in the org when they don't match the picture.

Hi @Lucas Scarin, 

The error shown in your screenshot typically appears when Einstein and Agentforce are not enabled or when the required access has not been provisioned in the org. If you're using a Trailhead Playground, try launching the challenge in a fresh playground and ensure you've completed all prerequisite setup steps from the module.

There is also a known issue where users may see the "Looks like you don't have access" message when accessing Agentforce Builder in certain environments. Also I have found below help article where it mentioned 

The workaround is to use the Legacy Builder. 

https://help.salesforce.com/s/articleView?id=005385944&type=1

Sometimes these errors happen randomly.   

If you have entered everything correctly and all the api names are

exactly as they should be from the module instructions, I have found that it can sometimes be resolved by:

1. opening an incognito chrome browser
2. logging into Trailhead
3. re-launching the playground
4. re-verifying the challenge in the incognito browser

Sometimes these errors happen randomly.   

If you have entered everything correctly and all the api names are

1. opening an incognito chrome browser
2. logging into Trailhead
3. re-launching the playground
4. re-verifying the challenge in the incognito browser