#Trailhead Superbadges28 utenti parlano di questo argomento

Hi @Dhwani V Ajmera

This generic “Whoops, looks like there was a problem” message in Superbadges usually means the challenge checker is not finding one of the required Flow elements exactly as expected.

For Create Equipment Malfunction Cases, I would recheck these areas:

1. Make sure you are working in the correct Superbadge org, not another Trailhead Playground.
2. Verify the Flow type, Flow name, and API name exactly match the challenge instructions.
3. Check all required objects, fields, conditions, assignments, and Create Records elements.
4. Make sure the Flow is saved and activated.
5. Confirm you didn’t add extra conditions or change any required API names.
6. Run Debug with the expected test data and confirm the case is actually created correctly.
7. If everything is correct, log out/in, refresh Trailhead, and try the challenge checker again after a few minutes.

For Superbadges, even a small mismatch in a resource/API name or condition can cause this generic error.

If possible, share a screenshot of the Flow elements/configuration. That will make it easier to identify exactly what the checker is missing. 

Thank you, 

Venkat Yadav.

@Ebony Williams

You’re probably not missing anything in the org setup. A couple of those actions are expected to be created/configured as Flow-based agent actions rather than showing up as ready-made actions.

I’d also check that you’re working in the correct Superbadge playground/org and that Agentforce is fully enabled before troubleshooting the individual actions.

Hello @Caroline Fearey concerning the action, check your API name; it is written " Label the action Translate Survey Input with API name Translate_Survey_Input using any description you’d like". Yours has an extra "Fitness" in it.Eric

Hi Melanie, could you first verify that the Program_Recommendation_Invocable Apex class was created successfully and that there are no compilation errors? 

Also, make sure you’re using the correct Trailhead Playground/org associated with the challenge. If the class is present and valid but still doesn’t appear in the Apex resource list, please share a screenshot of the Apex class and any error messages you’re seeing. That would help narrow down the issue. 

Hi Sandhya, the screenshot indicates that the org is waiting for email verification (“Almost there... Please check your email to confirm your new account”). 

Please check the email inbox and spam/junk folder for the verification email and complete the verification first. After verifying the email, try creating the credential again. 

If you’re not receiving the verification email, try resending the verification email and make sure you’re using a valid email address that you can access. Also, avoid creating multiple credentials with different email IDs until the original org is verified. 

If the verification email still doesn’t arrive after trying this, you may need to create a Salesforce Support case with the Trailhead org/credential details so Salesforce can check the account verification issue. 

Hi Patrice, since the assignments are completed but the Challenge Check is returning only a generic “Looks like something went wrong” message, it may be difficult to determine the issue from the screenshot alone. 

Could you share a screenshot of your Prompt Template configuration, the Record-Triggered Flow, and the resource references you used? Also, please confirm that Einstein Generative AI is enabled in the org. 

For the Launch issue, if the Salesforce Developer org isn't opening from the Launch button, try opening the copied URL in a new browser tab and make sure you're logged into the correct Trailhead account/org. 

If everything matches the challenge requirements and the Challenge Check still returns the generic error, it may be worth creating a Salesforce Support case with the challenge name and screenshot of the error. 

Hi Roger, the error in your screenshot indicates that the issue is with the General FAQ topic configuration, specifically the override not being configured correctly. 

For this step, make sure the General FAQ standard topic is configured with the required custom action/prompt template from the challenge, rather than trying to delete the standard action itself. 

I’d recommend going back to Agentforce Builder → General FAQ → Actions/Overrides and verify that the override points to the expected custom action and that the action is configured exactly as specified in the challenge instructions. 

After saving/publishing the changes, create a new version if required and run Check Challenge again.

Hi Oleksandr, your understanding is close, but the important part is that the Queueable job enqueued from the scheduled Apex is a second level of asynchronous execution. 

Test.stopTest() causes the scheduled job to execute, so your WarehouseSyncSchedule.execute() runs. When it calls System.enqueueJob(), the Queueable is placed in the async queue, but you shouldn't rely on that second-level async job executing within the same test context. 

For the Apex Specialist requirement, you can assert that the scheduled job was created and that the scheduled execution completes without exception. You can also query AsyncApexJob before/after the appropriate point to verify the Queueable was enqueued.

The production implementation should use:

public void execute(SchedulableContext ctx) {
    System.enqueueJob(new WarehouseCalloutService());
}

and the Queueable should implement Database.AllowsCallouts.

For the callout itself, use Test.setMock(HttpCalloutMock.class, ...) before Test.stopTest().

So the key distinction is:

Test.startTest() → System.schedule() → Test.stopTest() → Scheduled Apex executes → Queueable is enqueued

You don't need to make the scheduled class perform the callout directly; the Queueable is the correct pattern for a callout from scheduled Apex.