function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
Rahul Raghunathan 22Rahul Raghunathan 22 

Process Automation Specialist Super Badge error: MUNHENQM

Hi, I am working on the Process Automation Super Badge. When I am trying to submit my challenge I get an error
Challenge Not yet complete... here's what's wrong: 
There was an unexpected error while verifying this challenge. Usually this is due to some pre-existing configuration or code in the challenge Org. We recommend using a new Developer Edition (DE) to check this challenge. If you're using a new DE and seeing this error, please post to the developer forums and reference error id: MUNHENQM
Not sure what is wrong as I am using a brand new playground. Could some help me out here?
 
Best Answer chosen by Rahul Raghunathan 22
Stevie Burt 7Stevie Burt 7
@Rahul What is your validation rule? I split mine in two different ones. One for the country and one for the state.

COUNTRY:
NOT(
    OR(
       Country = "US", 
       Country = "USA", 
       ISBLANK( Country )
        )
     )

STATE:
OR( 
   LEN(State) <> 2, 
   NOT(CONTAINS("AL:AK:AZ:AR:CA:CO:CT:DE:DC:FL:GA:HI:ID:" & 
                "IL:IN:IA:KS:KY:LA:ME:MD:MA:MI:MN:MS:MO:MT:NE:NV:NH:" & 
                "NJ:NM:NY:NC:ND:OH:OK:OR:PA:RI:SC:SD:TN:TX:UT:VT:VA:" & 
                "WA:WV:WI:WY:PR", State))
   )

 

All Answers

NagendraNagendra (Salesforce Developers) 
Hi Rahul,

Sorry for this issue that you're encountering.

Can you please double check that your Developer Edition Org does not have any namespaces setup in it?Trailhead does not support namespaced DE Orgs and so if you have a namespace registered for the DE Org, you'll need to sign up for a new one and complete this module there.

When trying trailhead, we encourage users to create new Dev Org's such that the previous config changes do not affect the trailhead challenge settings.

To login into trailhead you can use your old org but for activity(code and config) related changes you can use new org. In such a way all point will add in your old profile only.

Please check the below link for help.​
http://https://developer.salesforce.com/page/Trailhead_FAQ
Please mark this as solved if the information helps.

Regards,
Nagendra.
Olivier ROlivier R
Same here on Step 1 .. If you're using a new DE and seeing this error, please post to the developer forums and reference error id: KXVGOKSJ ..
Created a new Trailhead Playground .. Error
Created a new DE, installed the Process Automation superbadge unmanaged package .. Error
Is this an error because the implementation is not right or a random technical error ?
Stevie Burt 7Stevie Burt 7
I was getting that error too but was able to get past it once I fixed my validation rule error to be on the field and NOT at the top of the page. Not sure why though since that isn't specified. But it worked. Now Im stuck on Step 4 with that same error! 
Rahul Raghunathan 22Rahul Raghunathan 22
@Nagendra,
I am using a new trailhead playground. I tried again but the same result.

@Stevie,
I tried what you said. But I am still getting the same error.
Stevie Burt 7Stevie Burt 7
@Rahul What is your validation rule? I split mine in two different ones. One for the country and one for the state.

COUNTRY:
NOT(
    OR(
       Country = "US", 
       Country = "USA", 
       ISBLANK( Country )
        )
     )

STATE:
OR( 
   LEN(State) <> 2, 
   NOT(CONTAINS("AL:AK:AZ:AR:CA:CO:CT:DE:DC:FL:GA:HI:ID:" & 
                "IL:IN:IA:KS:KY:LA:ME:MD:MA:MI:MN:MS:MO:MT:NE:NV:NH:" & 
                "NJ:NM:NY:NC:ND:OH:OK:OR:PA:RI:SC:SD:TN:TX:UT:VT:VA:" & 
                "WA:WV:WI:WY:PR", State))
   )

 
This was selected as the best answer
Rahul Raghunathan 22Rahul Raghunathan 22
@Stevie,

You are right. As soon as I split the validation rule it started working.. Thanks
Krishna RaviKrishna Ravi
Yes, It worked fine after splitting the validation rule.
kamesh sangilikamesh sangili
For me it worked after
AND(Splitting the rule per Steve's suggeston, Moving the error Location to 'Field' from 'Top of page')
Emily DuncanEmily Duncan
This worked for me as well - splitting the two and moving the error location to 'Field' for each of them. Thanks for all of the help, everyone!