Raised from #1891 and related to #2020
When provisioning Microsoft Teams teams using the teams team add command, on some occasions an error can be thrown, No team found with Group Id <id>.
UnhandledPromiseRejectionWarning: StatusCodeError: 404 - {"error":{"code":"NotFound","message":"No team found with Group Id 58c19f12-6bb5-4846-8ccd-36d9eb04ef2a","i nnerError":{"date":"2020-10-25T08:59:38","request-id":"083e431a-deb6-4f85-987e-a59487c18cea","client-request-id":"083e431a-deb6-4f85-987e-a59487c18cea"}}}The Microsoft Team is being created but the operation to retrieve group information which we return to the prompt fails because the Microsoft Graph has not updated accordingly and the newly created group cannot be found.
Whilst this is not specifically a bug in the CLI, we should add defensive code to handle scenarios where the Microsoft Graph does not return recently created objects in a timely manner.
As discussed in the related issue, the consensus is to include a loop into the code which returns the Group object, which will wait till the Group has been created and is returned successfully from the Graph.
Raised from #1891 and related to #2020
When provisioning Microsoft Teams teams using the
teams team addcommand, on some occasions an error can be thrown,No team found with Group Id <id>.The Microsoft Team is being created but the operation to retrieve group information which we return to the prompt fails because the Microsoft Graph has not updated accordingly and the newly created group cannot be found.
Whilst this is not specifically a bug in the CLI, we should add defensive code to handle scenarios where the Microsoft Graph does not return recently created objects in a timely manner.
As discussed in the related issue, the consensus is to include a loop into the code which returns the Group object, which will wait till the Group has been created and is returned successfully from the Graph.