I create a new Team using POST to https://graph.microsoft.com/v1.0/teams.
I expect TeamsAsyncOperation to complete with status “succeeded” but instead it stays with status “notStarted” but the Team is really created.
<code>{
"@odata.context": "https://graph.microsoft.com/v1.0/$metadata#teams('sqdfsdfs')/operations/$entity",
"id": "qsdfsqdfqsdf",
"operationType": "createTeam",
"createdDateTime": "2024-06-10T15:07:57.08827Z",
"status": "notStarted",
"lastActionDateTime": "2024-06-10T15:07:57.08827Z",
"attemptsCount": 1,
"targetResourceId": "70ef1c22-7ac1-4da6-a979-ac49b97559f4",
"targetResourceLocation": "/teams('qsdfsqdfsqdf')",
"Value": "{"apps":[],"channels":[],"WorkflowId":"westeurope.4b9c94e9-aa41-4891-b4b7-09aa5d89d91b"}",
"error": null
}
</code>
<code>{
"@odata.context": "https://graph.microsoft.com/v1.0/$metadata#teams('sqdfsdfs')/operations/$entity",
"id": "qsdfsqdfqsdf",
"operationType": "createTeam",
"createdDateTime": "2024-06-10T15:07:57.08827Z",
"status": "notStarted",
"lastActionDateTime": "2024-06-10T15:07:57.08827Z",
"attemptsCount": 1,
"targetResourceId": "70ef1c22-7ac1-4da6-a979-ac49b97559f4",
"targetResourceLocation": "/teams('qsdfsqdfsqdf')",
"Value": "{"apps":[],"channels":[],"WorkflowId":"westeurope.4b9c94e9-aa41-4891-b4b7-09aa5d89d91b"}",
"error": null
}
</code>
{
"@odata.context": "https://graph.microsoft.com/v1.0/$metadata#teams('sqdfsdfs')/operations/$entity",
"id": "qsdfsqdfqsdf",
"operationType": "createTeam",
"createdDateTime": "2024-06-10T15:07:57.08827Z",
"status": "notStarted",
"lastActionDateTime": "2024-06-10T15:07:57.08827Z",
"attemptsCount": 1,
"targetResourceId": "70ef1c22-7ac1-4da6-a979-ac49b97559f4",
"targetResourceLocation": "/teams('qsdfsqdfsqdf')",
"Value": "{"apps":[],"channels":[],"WorkflowId":"westeurope.4b9c94e9-aa41-4891-b4b7-09aa5d89d91b"}",
"error": null
}
What is the correct way to assume that the Teams is created if I can’t rely on the operation status?
New contributor
Antoine D is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.