+ Start a Discussion
Cynthia Hamilton NZCynthia Hamilton NZ 

Trailhead challenge error - Workflow Rule Migration

I've tried a second time using a brand new Trailhead Playground, and still get the error when checking the challenge:
"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: VRHJDGJD "
Brian KesslerBrian Kessler
I'm getting a very similar error, though my error id is "KATMTNEY".
Alap MistryAlap Mistry
Hello Cynthia and Brian, I don't know that which unit gives this error to both. Please can you specify unit name or question name?
 
Alap MistryAlap Mistry
I know only trail name, but don't have idea about unit. So please specify name of unit. So i will help you both.
Alap MistryAlap Mistry
For this error don't change your org.
Brian KesslerBrian Kessler
For me, it's:

Trail: Automate Your Business Process (https://trailhead.salesforce.com/trails/automate_business_processes)
Module: Workflow Rule Migration (https://trailhead.salesforce.com/trails/automate_business_processes/modules/workflow_migration)
Unit: Map Your Workflow Criteria to Process Criteria (https://trailhead.salesforce.com/trails/automate_business_processes/modules/workflow_migration/units/workflow_migration_criteria)

Org is/was a brand new developer org on eu11.

While waiting for a response, I just started following the "Use Salesforce Lightning Design System to Build a Prototype" unit of "UX Prototype Basics", for which I've set (but not yet deployed) the "My Domain".  (I've made some other changes, but they seem less relevant.)
Alap MistryAlap Mistry
User-added image

User-added image

User-added image

User-added image

User-added image

Check it out and make it as best answer.
Brian KesslerBrian Kessler
Hi @Alap Mistry,

I've tried following your screenshots and made some progress, but eventually got back to a variant of the original error message with reference error id: GZVIXJKI
 
Andrew ChabotAndrew Chabot
I am getting the error under the Slaes Reports for Lightning Experience - Extend Reports with Dashboards and Apps and my error code is: LKADQBCY    Please advise.
Brian KesslerBrian Kessler
@Andrew Chabot,
I'm afraid I can't advise you well, but @Cynthia Hamilton NZ's original thread was about the new Workflow Rule Migration module, which is where I'm also having my problem.

For the sake of keeping clarity and sanity in this thread, since you seem to be working on a different module, may I kindly suggest starting a new thread for it?

(Also, that might help bring it to the attention of those better aquaintained with the module you are working on and make any responses easier for others to find when they run into the same problem.)

-Brian.
 
Michele Losch 4Michele Losch 4
Hi All,
I'm also receving the same error in the Map Your Workflow Criteria to Process Criteria module, my reference code is FQCKWKNM
Lawrence PfaffLawrence Pfaff
I am also receiving the error with the Map Your Workflow Criteria to Process Criteria module

"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: MIXWFXGP"

and there is another thread describing this issue with no answer.

https://developer.salesforce.com/forums/?id=9060G000000IAZUQA4
 
Nicholle MinchNicholle Minch
I'm receiving the same error with the Map Your Workflow Criteria to Process Criteria module.  I tried all that is listed on this thread with no luck.   
Alap MistryAlap Mistry
Hi all, I passed this challenge with help of above screenshots. I suggest that you can change your org and build new process with same name and refer workflow rules for this challenge which is in package and you ensure that package is installed or not for this challenge.
Alap MistryAlap Mistry
Check this screenshot.

Check this screenshot. Next trail is Map Your Workflow Actions to Process Actions. So I passed Map Your Workflow Criteria to Process Criteria Challenge. If any other query related to this challenge, then post on this thread.
Cynthia Hamilton NZCynthia Hamilton NZ
Thanks Alap for your answers - I have exactly the values you had in the screen shots and still the same error (different code).  I'll make a 3rd attempt tomorrow with a second brand new DE ...
Alap MistryAlap Mistry
Hello Cynthia,

        You make sure that package is installed or not for this challenge in your org.
Cynthia Hamilton NZCynthia Hamilton NZ
I've actually tried several combinations - 1) pre-existing dev org - package was installed - error 2) new trailhead playground where the package was installed - error (then reported) 3) another new dev org where the package was not installed - same error (different code of course) 4) that dev org in 3 with the package installed - same error I get sensible errors on variations in the New Opportunity criteria until I add a true or false in the condition
Alap MistryAlap Mistry
User-added image

Make sure that you configure like this.
Brian KesslerBrian Kessler
Hi Alap, 

I appreciate you are trying to help us and this works for you, but (as you may already know) SFDC is a quirk and tempermental platform.  
What works for one person in one org, may not work in any other context.

Presently this is still failing, with reference error id: RZXTISFF

This time,

1. I've created a new Playground (instead of a Dev org), URL: https://cunning-badger-391333-dev-ed.lightning.force.com/
2. I've ignored information about "Critical Updates" (instead of installing them).
3. Installed "Opportunity Management Workflow Rules" from https://login.salesforce.com/packaging/installPackage.apexp?p0=04t41000002FoDo
4. Created an "Opportunity Management" that starts when "A record changes".
5. Chose the "Opportunity" object and specified to start "when a record is created or edited".
6. Copied all your critieria above, cutting and pasting the criteria name from the unit specifications to ensure they were spelled and capitalized exactly.

There was one and only one observable variant in my org, my default currency was EUR, but changing this did not fix the problem.

If it helps, I've exported /flows/Opportunity_Management-1.flow... maybe you (or someone) can spot something wrong in the metadata:

It is far too long for one post, so I'll split it between the next few posts... maybe you can see something wrong with the metadata.

(Or if you send yours, I can diff them.)




 
Brian KesslerBrian Kessler
Flow Part 1:
?xml version="1.0" encoding="UTF-8"?>
<Flow xmlns="http://soap.sforce.com/2006/04/metadata">
    <assignments>
        <name>myVariable_waitStartTimeAssignment</name>
        <label>myVariable_waitStartTimeAssignment</label>
        <locationX>0</locationX>
        <locationY>0</locationY>
        <assignmentItems>
            <assignToReference>myVariable_waitStartTimeVariable</assignToReference>
            <operator>Assign</operator>
            <value>
                <elementReference>$Flow.CurrentDateTime</elementReference>
            </value>
        </assignmentItems>
        <connector>
            <targetReference>myDecision</targetReference>
        </connector>
    </assignments>
    <decisions>
        <processMetadataValues>
            <name>index</name>
            <value>
                <numberValue>0.0</numberValue>
            </value>
        </processMetadataValues>
        <name>myDecision</name>
        <label>myDecision</label>
        <locationX>50</locationX>
        <locationY>0</locationY>
        <defaultConnector>
            <targetReference>myDecision2</targetReference>
        </defaultConnector>
        <defaultConnectorLabel>default</defaultConnectorLabel>
        <rules>
            <name>myRule_1</name>
            <conditionLogic>and</conditionLogic>
            <conditions>
                <processMetadataValues>
                    <name>inputDataType</name>
                    <value>
                        <stringValue>Picklist</stringValue>
                    </value>
                </processMetadataValues>
                <processMetadataValues>
                    <name>leftHandSideType</name>
                    <value>
                        <stringValue>Picklist</stringValue>
                    </value>
                </processMetadataValues>
                <processMetadataValues>
                    <name>operatorDataType</name>
                    <value>
                        <stringValue>String</stringValue>
                    </value>
                </processMetadataValues>
                <processMetadataValues>
                    <name>rightHandSideType</name>
                    <value>
                        <stringValue>Picklist</stringValue>
                    </value>
                </processMetadataValues>
                <leftValueReference>myVariable_current.StageName</leftValueReference>
                <operator>EqualTo</operator>
                <rightValue>
                    <stringValue>Closed Lost</stringValue>
                </rightValue>
            </conditions>
            <conditions>
                <processMetadataValues>
                    <name>inputDataType</name>
                    <value>
                        <stringValue>Currency</stringValue>
                    </value>
                </processMetadataValues>
                <processMetadataValues>
                    <name>leftHandSideType</name>
                    <value>
                        <stringValue>Currency</stringValue>
                    </value>
                </processMetadataValues>
                <processMetadataValues>
                    <name>operatorDataType</name>
                    <value>
                        <stringValue>Currency</stringValue>
                    </value>
                </processMetadataValues>
                <processMetadataValues>
                    <name>rightHandSideType</name>
                    <value>
                        <stringValue>Currency</stringValue>
                    </value>
                </processMetadataValues>
                <leftValueReference>myVariable_current.Amount</leftValueReference>
                <operator>GreaterThanOrEqualTo</operator>
                <rightValue>
                    <numberValue>100000.0</numberValue>
                </rightValue>
            </conditions>
            <connector>
                <targetReference>myRule_1_pmetdec</targetReference>
            </connector>
            <label>Closed Lost and High-Value</label>
        </rules>
    </decisions>
    <decisions>
        <processMetadataValues>
            <name>index</name>
            <value>
                <numberValue>1.0</numberValue>
            </value>
        </processMetadataValues>
        <name>myDecision2</name>
        <label>myDecision2</label>
        <locationX>50</locationX>
        <locationY>0</locationY>
        <defaultConnector>
            <targetReference>myDecision4</targetReference>
        </defaultConnector>
        <defaultConnectorLabel>default</defaultConnectorLabel>
        <rules>
            <name>myRule_3</name>
            <conditionLogic>and</conditionLogic>
            <conditions>
                <processMetadataValues>
                    <name>inputDataType</name>
                    <value>
                        <stringValue>Picklist</stringValue>
                    </value>
                </processMetadataValues>
                <processMetadataValues>
                    <name>leftHandSideType</name>
                    <value>
                        <stringValue>Picklist</stringValue>
                    </value>
                </processMetadataValues>
                <processMetadataValues>
                    <name>operatorDataType</name>
                    <value>
                        <stringValue>String</stringValue>
                    </value>
                </processMetadataValues>
                <processMetadataValues>
                    <name>rightHandSideType</name>
                    <value>
                        <stringValue>Picklist</stringValue>
                    </value>
                </processMetadataValues>
                <leftValueReference>myVariable_current.StageName</leftValueReference>
                <operator>EqualTo</operator>
                <rightValue>
                    <stringValue>Closed Lost</stringValue>
                </rightValue>
            </conditions>
            <connector>
                <targetReference>myRule_3_pmetdec</targetReference>
            </connector>
            <label>Closed Lost</label>
        </rules>
    </decisions>
    <decisions>
        <processMetadataValues>
            <name>index</name>
            <value>
                <numberValue>2.0</numberValue>
            </value>
        </processMetadataValues>
        <name>myDecision4</name>
        <label>myDecision4</label>
        <locationX>50</locationX>
        <locationY>0</locationY>
        <defaultConnector>
            <targetReference>myDecision6</targetReference>
        </defaultConnector>
        <defaultConnectorLabel>default</defaultConnectorLabel>
        <rules>
            <name>myRule_5</name>
            <conditionLogic>and</conditionLogic>
            <conditions>
                <processMetadataValues>
                    <name>inputDataType</name>
                    <value>
                        <stringValue>Picklist</stringValue>
                    </value>
                </processMetadataValues>
                <processMetadataValues>
                    <name>leftHandSideType</name>
                    <value>
                        <stringValue>Picklist</stringValue>
                    </value>
                </processMetadataValues>
                <processMetadataValues>
                    <name>operatorDataType</name>
                    <value>
                        <stringValue>String</stringValue>
                    </value>
                </processMetadataValues>
                <processMetadataValues>
                    <name>rightHandSideType</name>
                    <value>
                        <stringValue>Picklist</stringValue>
                    </value>
                </processMetadataValues>
                <leftValueReference>myVariable_current.StageName</leftValueReference>
                <operator>EqualTo</operator>
                <rightValue>
                    <stringValue>Closed Won</stringValue>
                </rightValue>
            </conditions>
            <connector>
                <targetReference>myRule_5_pmetdec</targetReference>
            </connector>
            <label>Closed Won</label>
        </rules>
    </decisions>
    <decisions>
        <processMetadataValues>
            <name>index</name>
            <value>
                <numberValue>3.0</numberValue>
            </value>
        </processMetadataValues>
        <name>myDecision6</name>
        <label>myDecision6</label>
        <locationX>50</locationX>
        <locationY>0</locationY>
        <defaultConnector>
            <targetReference>myDecision8</targetReference>
        </defaultConnector>
        <defaultConnectorLabel>default</defaultConnectorLabel>
        <rules>
            <name>myRule_7</name>
            <conditionLogic>and</conditionLogic>
            <conditions>
                <leftValueReference>formula_myRule_7</leftValueReference>
                <operator>EqualTo</operator>
                <rightValue>
                    <booleanValue>true</booleanValue>
                </rightValue>
            </conditions>
            <label>New Opportunity</label>
        </rules>
    </decisions>
    <decisions>
        <processMetadataValues>
            <name>index</name>
            <value>
                <numberValue>4.0</numberValue>
            </value>
        </processMetadataValues>
        <name>myDecision8</name>
        <label>myDecision8</label>
        <locationX>50</locationX>
        <locationY>0</locationY>
        <defaultConnectorLabel>default</defaultConnectorLabel>
        <rules>
            <name>myRule_9</name>
            <conditionLogic>and</conditionLogic>
            <conditions>
                <processMetadataValues>
                    <name>inputDataType</name>
                    <value>
                        <stringValue>Picklist</stringValue>
                    </value>
                </processMetadataValues>
                <processMetadataValues>
                    <name>leftHandSideType</name>
                    <value>
                        <stringValue>Picklist</stringValue>
                    </value>
                </processMetadataValues>
                <processMetadataValues>
                    <name>operatorDataType</name>
                    <value>
                        <stringValue>String</stringValue>
                    </value>
                </processMetadataValues>
                <processMetadataValues>
                    <name>rightHandSideType</name>
                    <value>
                        <stringValue>Picklist</stringValue>
                    </value>
                </processMetadataValues>
                <leftValueReference>myVariable_current.StageName</leftValueReference>
                <operator>EqualTo</operator>
                <rightValue>
                    <stringValue>Negotiation/Review</stringValue>
                </rightValue>
            </conditions>



 
Brian KesslerBrian Kessler
Sorry, this won't let me post the rest.  :-(
Alap MistryAlap Mistry
Can you try to convert currency euro to dollar and set in opportunity amount? May be it's work for you.
Brian KesslerBrian Kessler
@Alap,

1. Added allowing recursion, which doesn't seem like it should be presently relevant, but it didn't help.
2. Unless there is somewhere else to change it, I've already converted "Currency Locale" to "USD" in Company Information / Organization Details.

Not sure what you mean by "set in opportunity amount".  Please elaborate.

Thanks,
-Brian.

 
Alap MistryAlap Mistry
I said that convert 100000 dollar in euro (93131.55 euro) and set it in opportunity amount value which is in Closed Lost and High-Value and Negotiation and High-Value Criteria.
Brian KesslerBrian Kessler
My values are already in USD now. Converting didn't change the numeric values and they now each read "$100,000" as expected.
Alap MistryAlap Mistry
I don't know why are you facing this error? Please check your process again and check error. If any error occur, then post it here.
Lawrence PfaffLawrence Pfaff
I have tested this by making 3 new DE's and checking at every step. I found that if I take out the ISNEW() from the New Opportunity Node the error changes to:

Challenge Not yet complete... here's what's wrong: 
Criteria node ‘New Opportunity’ isn’t properly configured. Make sure that the formula matches the filter conditions in the “When created, select Active Opportunity on account” workflow rule and checks whether the record is new.

From:

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: ZUQISZEC

when the ISNEW() function is added back to the node criteria.
Alap MistryAlap Mistry
Please refer my screenshots and also refer workflow rule for this challenge which is given in package.
Lawrence PfaffLawrence Pfaff
My setup is identicle to your screenshots and I have been through the workflow rules many times. Something else is going on here. Salesforce needs to evaluate the validation or the ISNEW() function.
Alap MistryAlap Mistry
Don' add field in Formula editor manually. Use it's built-in functions.
Michele Losch 4Michele Losch 4
After I created each node I would check the challenge to see when the error message "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: DYPXVIPR" would appear. This error only appears after creating the "New Opportunity" node. 
Lawrence PfaffLawrence Pfaff
I did use the built in functions.
Brian KesslerBrian Kessler
In order to bipass the limitations of this forum which wouldn't allow me to dump my Opportunity_Management-1.flow above, I've instead dumped all the metadata of my environment to:

https://github.com/nilvon9wo/opportunity-management-migration

The Process Builder metadata can be located at:

https://github.com/nilvon9wo/opportunity-management-migration/blob/master/src/flows/Opportunity_Management-1.flow

@Alap (or anyone who has passed this challenge), can you please diff this against an export of the metadata from your environment?


 
Kim SchaefgesKim Schaefges
I'm getting the same 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: QRWRTSDL
Candi WestCandi West

I'm getting the same error on the Hands-on Challenge for "Map Your Workflow Criteria to Process Criteria"

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: AXWLHYEW

I have tried it in my existing DE, a new completely blank DE, my existing Trailhead Playground and a fresh Trailhead Playground and I get the same message every time with the exception of the reference error id.

Kent Saxin Hammarström 11Kent Saxin Hammarström 11
Same here (Map Your Workflow Criteria to Process Criteria), except my error id is MSDOCBUP. 
Hmm, another attempt gives the same error message, but error id ILXFQAEQ. Seems like these ids don't actually identify the error, just a pointer into a log at Salesforce maybe. 
Shalom RubdiShalom Rubdi
Not an April's fool post!  Getting the same error after 2 attempts with fresh Trailhead playgrounds:

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: YHYPIARA
Shalom RubdiShalom Rubdi
Spun up a new dev org & tried yet again, thinking the error might be due to a property of the challenge environment (Playground vs. Dev Org).

Sadly, encountered the following error (le sigh):

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: MLCEIFFI
Brian KesslerBrian Kessler
1. Does anyone with the ability to do something with these reference error ids actually reading this forum?
2. Has anyone other than @Alap ever managed to pass this unit?
3. Will someone who passed this unit please export your environmental metadata so we can compare it against our own?
 
Hans LissHans Liss
I have the same problem, and I've been trying every conceivable action now, including *everything* mentioned in this thread, recreating everything from scratch a few times and even trying various minor changes directly in the metadata XML in the hope that the verification is choking on something that isn't visible in the Process Builder, but all to no avail.
I can confirm that the Advanced option has to be set correctly, and that the formula on New Opportunity must be "ISNEW() && [Opportunity].IsClosed <> true" or something very similar. Using NOT() or using the IsClosed value directly as a boolean value will, while correct, produce a normal error message. My conclusion is that there is probably something else in the org that causes the error message, but I can't find it. I've made sure language, locale, currency and even time zone are all set to typical US settings.
I hope that there's no penalty for trying to verify the challenge 30-40 times.
Hans LissHans Liss
If you're still stuck on this, try moving to the third unit, complete it and then retry try the challenge check in this one. It worked for me.
Hans LissHans Liss
Just to save you some time, read through this thread too, before moving on: https://developer.salesforce.com/forums/?id=9060G000000IAbGQAW
Shalom RubdiShalom Rubdi
I attempted the other units and completed those, but an issue persists with the 'Map Your Workflow Actions to Process Actions'...  I'll comment in the link that Hans posted
Brian KesslerBrian Kessler
@Hans Liss,
I've moved on (but not yet passed) the next challenge.
However, I am now able to successfully submit for this unit.

@whoever-writes-these tests,
Where did you learn to create automated tests?
First rule of testing: Test results, not implementation details!

 
Kent Saxin Hammarström 11Kent Saxin Hammarström 11
Well, that wasn't much fun. I went on to the next unit (and, incidentally, failed repeatedly for strange reasons), then went back to this one and magically it now passes. 
Hans LissHans Liss
@Kent Saxin Hammaström 11, check the other thread I linked for suggestions for some of the problems with the next unit.
Kent Saxin Hammarström 11Kent Saxin Hammarström 11
@Hans: Thanks. Actually, once I had gone back and passed this one, when I went back again to the next one that one passed too... ;)
I did change one thing only in between attempts: I re-ordered the actions for closed/won, from being in the order of the workflow to being in the order listed by the task.
Hans LissHans Liss
@Kent, oh that's weird. Maybe that's worth mentioning in the other thread too? Their challenge verification code seems to be a bit... picky, right now. :)
Nathan WylderNathan Wylder
I just got credit for this module by going on to the next one (Map Your Workflow Actions to Process Actions) completing that challenge and then backtracking and clicking on Check Challenge and it approved it. So, not sure what the issue was, but there was a lot of wasted time in the process...
Chris DuarteChris Duarte
Yes, I work on Trailhead and I'm reading your feedback now, and sending it directly to our team who worked on this content. We try to test the outcome, not the implementation itself, but that can be tricky at times to do. 
Brian KesslerBrian Kessler
@Chris Duarte,
If it is not possible to test the outcome, the task/subtask itself is bad.

When working on an agile project with a real client, each task should be something that gives a client real value.
There is no value in anything which can't be tested in the form:
Given that X is true, when I do Y, then Z will be true.

This logic might easily be applied to Trailhead.

Take, for instance, this present module.
Does it really make good sense as a development practice that first we work on all the criteria, but then it does nothing testable?

What happens when you go on to develop your actions, but they don't work?
You can't isolate the problem to your actions because maybe your earlier criteria were wrong.  Maybe, for example, an earlier criteria is catching the condition you wanted, so you aren't getting to your actions. 

It would be better to make one sub-process functional, including both the criteria and actions, and then test that each of the actions work correctly, and only then move on to creating the next sub-process.  If it doesn't work, you could then move it before existing sub-processes so you can test it in isolation.  That will tell you if the problem is in your actions or in your criteria.  Once you know the actions are working correctly, you will know the problem is with your criteria.


So, yes, in principle, I disagree with the very approach that this Trailhead is advocating for making the migration.


I could give feedback on what's wrong with other Trailheads and how they might be improved, but I don't want to further derail this thread.  (But I would be open to having that discussion in some other forum.)


 
Chris DuarteChris Duarte
Brian - the team is rewriting this challenge now. One of our rules is to not implement challenges with currency fields -- this is too complicated for reasons related to international currencies.

We are aware of other hands-on challenges in Trailhead that could use improvement. We're working on them one at a time. In some cases, it's the underlying logic that needs improvement (e.g., testing for the outcome), but in other cases, it's the challenge text that needs refinement, or the challenge should be completely rewritten, because the use case is bad.

It's not easy to write challenges that are (1) completely clear with no room for ambiguity (2) real world use cases (3) accessible for us with the APIs we have available for testing (this is a big one; we have real limitations on what we can actually test). We do our best. Thanks for the feedback. I'll update this thread once we've updated the challenge; hopefully in our next content release in about 3 weeks. 
Hans LissHans Liss
@Chris, It does get frustrating when you can't figure out how to tweak your answer to pass a challenge even when you know that you have done everything right, so it's a good thing that you are fixing it. I ran into similar problems with other modules, including at least one SuperBadge, and I'm sure your work with keeping these up-to-date and fixing bugs isn't going to end anytime soon. Still, I think you are doing a *very* good job with Trailhead. As far as I know, no other company has anything similar available for free, and it's awesome that you do!
Igor Androsov 5Igor Androsov 5
No matter what I try keep getting variations on error id: FBECLRIX. error id: XMYSIXFD  on Map Your Workflow Criteria to Process Criteria
  step validation it's always different error code. something is not right with my Trailhead account if others could pass this step it makes no sense. 
Michele Losch 4Michele Losch 4
@Igor,

I had the same issue. I moved onto the next module "Map Your Workflow Process Actions" completed that module then went back to the Criteria and was finally able to pass. 

Michele 
Claudio Bruno 8Claudio Bruno 8
Hello,
I have referred to Alap's screenshot, but trailhead did this error: "Challenge Not yet complete... here's what's wrong:
The end behavior for the ‘Closed Lost’ criteria node isn’t properly configured.". In this node, I added the following action immediate User-added image
I just started with process builder. Suggestions?

Thanks in advance,
Claudio
Alap MistryAlap Mistry
Hi Claudio Bruno 8,
I think you active your process. Deactivate it and clone it and make new version of process (Not Activated). Then check your challenge.
If it is helpful, then make it as Best Answer.
Regards,
Alap Mistry
Claudio Bruno 8Claudio Bruno 8
Hi Alap,
I tried to do as you said, but the error is still the same: "Criteria node 'Closed Lost' isn’t properly configured. Make sure that the advanced option is selected.".
Kind regards,
Claudio 
Alap MistryAlap Mistry
Hi Claudio Bruno 8,
As per your error, click on Closed Lost criteria and select checkbox under Advanced section.
Regards,
Alap Mistry
Igor Androsov 5Igor Androsov 5
Hi 
Claudio Bruno 8 I was stuck on this step for several days with multiple Playground & DE orgs. Finally try one recommended path skip that step did next step - add all actions, passed #3 step with actions. Then return to step #2 tested it passed. Did the trick
Claudio Bruno 8Claudio Bruno 8
Hello,
I solved the problem by following the advice of Alap and I passed my Challenge.
Than you all for the support.
Have a nice day,
Claudio
Alap MistryAlap Mistry
@Claudio Bruno 8,
Welcome Claudio Bruno 8.
Regards,
Alap Mistry
Mahalingam Selvaraj 9Mahalingam Selvaraj 9
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: HBGQHNWK

Multiple versions of the same error with different error codes.

Will try the next module and come back to this.

Thanks for the guidance!
Mahalingam Selvaraj 9Mahalingam Selvaraj 9
Thanks for the help @Igor Androsov 5, skipping the step and validating after the next step worked :) Made my day :)
Sandeep YadavSandeep Yadav
In this unit you have to create only a process named Opportunity Management and start the process When a record changes 
don't more work except this(explained above).
All the work is donr in next unit of this module