Which lab?
mcs-tools
What happened?
UC # 2 has you create a new classic agent named Sales Commission (and add the agent flow as a tool). But the solution containing that agent — with the flow tool already added — is already imported in the lab environment. Creating a new agent with the same name fails due to the duplicate, so the use case can't be completed as written.
Suggested fix (for the instructions):
- Remove Use Case # 2 entirely — agent flows are covered in their own dedicated lab, so this use case is redundant here.
- Promote the Extra Credit (CUA) use case to be Use Case # 4.
- Renumber the remaining use cases: current UC # 3 → UC # 2, current UC # 4 → UC # 3.
- (If UC # 2 is kept instead of removed, at minimum give the agent a different name to avoid the duplicate-name collision with the pre-imported solution.)
What did you expect?
That UC # 2 could be completed from a clean state, or that the pre-imported solution wouldn't collide with the agent you're instructed to create.
Steps to reproduce
- Open the lab environment (which already has the solution with the Sales Commission agent + flow tool imported).
- Follow UC # 2: from the Agents list, create a New classic agent named Sales Commission.
- Observe: creation fails because an agent with that name already exists in the environment.
Screenshots

Which lab?
mcs-tools
What happened?
UC # 2 has you create a new classic agent named Sales Commission (and add the agent flow as a tool). But the solution containing that agent — with the flow tool already added — is already imported in the lab environment. Creating a new agent with the same name fails due to the duplicate, so the use case can't be completed as written.
Suggested fix (for the instructions):
What did you expect?
That UC # 2 could be completed from a clean state, or that the pre-imported solution wouldn't collide with the agent you're instructed to create.
Steps to reproduce
Screenshots