+ Start a Discussion
Yury BondarauYury Bondarau 

Issue in trailhead super badge "Reports & Dashboards". Issue: TQQJZXRV

I got the following error when trying to pass salesforce Reports & Dashboards superbadge challenge ( https://developer.salesforce.com/trailhead/en/super_badges/superbadge_reports)

User-added image

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


I created fresh org for this challenge, so I do not think the issue can be caused by existing customiztions.

Could somebody describe what TQQJZXRV code means?
Yury BondarauYury Bondarau
When try to check the challenge next time it returns the following number:
EXLIEZXU
Yury BondarauYury Bondarau
New Code - ALKINIHL
Amit Chaudhary 8Amit Chaudhary 8
If NameSpace or domain is enable in your org ? If yes then please create developer org and try again .

Please check below trailhead FAQ
1) https://developer.salesforce.com/page/Trailhead_FAQ

I think my work is correct, but the challenge verification is still giving me an error.
If you think you've completed the challenge correctly, but you are still getting errors, make sure that you are using a fresh Developer Edition that does not have a namespace prefix. (What is a namespace prefix?) If you are still having trouble, use the “Share Feedback” button in the footer or on the right column to send a support request.

Let us know if this will help you
 
Yury BondarauYury Bondarau

Hi Amit,

Thank you for your response. As I said, this is completely new salesforce org created especially for this trailhead super badge.

Do you work in salesforce support? Can somebody explain what these exception codes mean?

 

Yury BondarauYury Bondarau
This issue was solved somehow. Just logged in 2 days after the error occured and everything were fine.