Module:
Agent Customization with Flows → Add a Flow as an Agent Action (Agentblazer Legend 2026)
Org username: sy.linda.kang@daeunextier.com_flowretry
Summary
The challenge grader looks for an agent named Coral Cloud Booking Agent, but the org I was provisioned ships with Coral Cloud Experience Agent
instead. I believe this was caused by a provisioning outage on the DE org sign-up site on Friday, June 26 (KST). As a result, the challenge cannot be passed, no matter how the configuration is done.
Error message
The core mismatch
The unit instructions consistently say "Coral Cloud Booking Agent" (e.g., "In the Agents list, select Coral Cloud Booking Agent"). However, no step in this unit or any prior unit creates or renames an agent to "Coral Cloud Booking Agent" — it is supposed to already exist in the org.
Root cause: provisioning outage on June 26 (KST)
This is the key part. The timeline of facts:
- On Friday, June 26 (KST), the DE org sign-up site for this badge was down due to a provisioning error. It displayed: "Oops! We could not find the requested promotion org. The requested org could not be found in our database or the org has expired." I also received a follow-up email from support@emea.salesforce.com confirming a temporary technical issue with org registration that the team was aware of and working to resolve. (Both screenshots attached.)
- The site was restored a few hours later, but residual errors remained — some orgs were created but failed to register/connect properly.
- A colleague who provisioned their DE org before the outage completed the exact same steps I did and received an org that correctly contains "Coral Cloud Booking Agent."
- I provisioned my org after the outage, and every org I receive — even after multiple fresh provisioning attempts — contains "Coral Cloud Experience Agent" only instead of "Coral Cloud Booking Agent."
This before/after comparison strongly indicates that the outage left the org provisioning template in a bad state, so orgs created after June 26 are missing the correct "Coral Cloud Booking Agent" and ship with the older "Coral Cloud Experience Agent" instead.
What I tried (and why it can't work)
- Renamed the agent's label to "Coral Cloud Booking Agent" just to pass the trail → still fails, probably because the API Name remains Coral_Cloud_Experience_Agent, and API names cannot be changed after creation.
- Provisioned multiple brand-new orgs and reconfigured everything from scratch → every org still ships with "Coral Cloud Experience Agent."
Conclusion / Request
Because the correct base agent ("Coral Cloud Booking Agent") is missing from every org provisioned after the June 26 outage, this challenge is impossible to pass through any user-side action. Could the team please:
- Confirm whether the org provisioning template for this badge was affected by the June 26 outage, and
- Fix the provisioning template (or otherwise issue a correctly-configured org) so that newly provisioned orgs include "Coral Cloud Booking Agent" as expected?
Thank you very much for your help.
