ghost
commented
2 years ago Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @sgellock.
Issue Details
After tested, we found API failed to create Bot Direct Line Speech immediately after the cognitive account is created successfully. But Bot Direct Line Speech can be created successfully at second apply with same request payload. Though the cognitive account is created successfully and API returned, but seems the primary access key returned by the cognitive account isn't ready yet. Could you take a look this issue? Thanks in advance. Error Message: ``` botservice.ChannelsClient#Create: Failure responding to request: StatusCode=400 -- Original Error: autorest/azure: Service returned an error. Status=400 Code="InvalidChannelData" Message="ChannelConverter Exception: DirectLine Speech Channel failed to acquire Cognitive subscription id from tokenEndpoint." ``` Repro steps: 1. Create resource group 2. Create Bot Channel Registration 3. Create Cognitive Account 4. Immediately create Bot Direct Line Speech after the cognitive account is created successfully 5. Until now, you will see API failed and threw above error message
| Author: | neil-yechenwei |
|---|---|
| Assignees: | - |
| Labels: | `Service Attention`, `Bot Service`, `needs-triage` |
| Milestone: | - |
After tested, we found API failed to create Bot Direct Line Speech immediately after the cognitive account is created successfully. But Bot Direct Line Speech can be created successfully at second apply with same request payload.
Though the cognitive account is created successfully and API returned, but seems the primary access key returned by the cognitive account isn't ready yet. So I think it's the bug on Cognitive Account. Cognitive Account service should return "status = 200" when the resource is completely deployed. Could you take a look this issue? Thanks in advance.
Error Message:
Repro steps: