Hi Alice,
we're experieincing the same issue and it's clearly because the nevironment cannot link to the required CDS instance.
We're unable to pick for the field "Organization Name" any value expected to be offered through that "missing link" so all we're able to set is custom values that always result into the flow failing.
Here you go the Error Details:
{
"status": 409,
"message": "The environment 'Default-763fb31b-4ea0-4888-9381-9293dee0fde1' is not linked to a new CDS 2.0 instance. The operation 'ListInstanceMetadata' is forbidden for unlinked environments.",
"source": "api.bap.microsoft.com",
"errors": [],
"debugInfo": "clientRequestId: 80b4623f-f1c8-423b-b1fe-71c9bde70ed1"
}
Just FYI, the flow that we're using was created starting from the template called "Get an email report of approvals waiting for my response".
Thanks very much in advance for any help you may be able to offer to get around that prob,
Cristina Martin