Bug: Cannot activate "Agent Compliance | Approve Case (Child)" flow - dependent workflow also fails to activate

Description

While following the Compliance Hub setup wizard, attempting to activate the cloud flow "Agent Compliance | Approve Case (Child)" fails with the following error:

"The workflow with id '....' cannot be used as a child workflow because it has never been published. Child workflows need to be published at least once before they can be included in a published parent workflow."

I attempted to resolve this by locating the dependent workflow with the ID and activating it independently first, as instructed in the setup documentation (Grandchild → Child → rest of the flows order). However, the dependent workflow itself also fails to activate, which blocks the parent "Approve Case (Child)" flow from ever being published.

Steps to reproduce

1. Go to Solutions > Copilot Studio Accelerator > Cloud flows
2. Run the Setup Wizard and proceed to the "Activate Flows" step
3. Attempt to turn on "Agent Compliance | Approve Case (Child)"
4. Observe the "Failed to activate the process" error
5. Attempt to manually locate and activate the dependent grandchild workflow (id: ...)
6. Observe that this flow also fails to activate

Expected behavior

The "Agent Compliance | Approve Case (Child)" flow (and its dependent grandchild workflow) should activate successfully when following the order specified in the setup documentation (Grandchild flows first, then Child flows, then the rest), allowing the Compliance Hub setup wizard to be completed.

Actual behavior

The "Agent Compliance | Approve Case (Child)" flow fails to activate with the error:

"The workflow with id '...' cannot be used as a child workflow because it has never been published. Child workflows need to be published at least once before they can be included in a published parent workflow."

Attempting to manually activate the referenced grandchild workflow (id: ...) independently also fails, which means the dependency can never be satisfied and the parent flow remains permanently unable to activate.

Environment

No response

Additional context or logs

No response