You need to sign in to do that
Don't have an account?
Cynthia 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 "
"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 "
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.)
Check it out and make it as best answer.
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
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.
I'm also receving the same error in the Map Your Workflow Criteria to Process Criteria module, my reference code is FQCKWKNM
"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
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.
You make sure that package is installed or not for this challenge in your org.
Make sure that you configure like this.
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.)
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.
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.
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.
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?
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
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.
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.
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
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
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?
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.
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!
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.
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.)
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.
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.
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
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
I just started with process builder. Suggestions?
Thanks in advance,
Claudio
Regards,
Alap Mistry
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 Mistry
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
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 Mistry
Multiple versions of the same error with different error codes.
Will try the next module and come back to this.
Thanks for the guidance!
don't more work except this(explained above).
All the work is donr in next unit of this module
Greetings!
Please clean your browser's cache and cookies and try again to check your answer using trailhead.
If still facing a problem, please reach out to the trailhead support team.
Thank you!
Regards,
Suraj Tripathi