#Trailhead Challenges1,171 discussing

Hey Melanie, 

Your setup in the screenshot matches the official steps exactly (Name, Action: Add, Product: Laptop Pro Bundle), so the immediate fields look correct. A few things worth checking given the exact wording of the checker error: 

1. Confirm the record actually saved, not just appears in the panel. Go back to the main Laptop Pro Master Orchestration workspace view (close the side panel entirely) and check if "Scenario Laptop Pro Invoicing" shows up in the Scenarios list under Invoicing there, not just inside the panel you had open when creating it. 

2. Double-check exact spelling/capitalization, "Scenario Laptop Pro Invoicing" needs to match character-for-character (the checker is typically case- and space-sensitive). 

3. Per the official steps, this same pattern (create a scenario per fulfillment step group) needs to be repeated across other lanes too, not just Invoicing. If the challenge checker validates all expected scenarios together and one from another lane is missing or misnamed, it can sometimes surface the error against a different scenario name than the one actually missing. Worth confirming all your lanes (Inventory Management, etc.) have their expected scenarios created too, not just Invoicing. 

4. Refresh the page fully after saving, sometimes the panel doesn't reflect a true save until a hard refresh. 

Reference:

Hi @Nikhil Kawale, 

Thank you for sharing but I  have carefully followed the exact steps provided in the module (

https://trailhead.salesforce.com/content/learn/modules/complex-order-decomposition-and-orchestration-with-revenue-cloud/define-dependencies-and-fulfillment-scenarios?trail_id=prepare-for-your-salesforce-revenue-cloud-consultant-exam) and have attached a screenshot of my Fulfillment Workspace for reference. However, I am still encountering the same error. To rule out any setup-related issues, I have also created multiple new playgrounds and repeated the entire process from the beginning several times, but the issue persists and none of the attempts have been successful.

Could you please review the attached screenshot and help identify the root cause of the problem? Any guidance would be greatly appreciated.