You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Async behaviour: "Resource does not exist" at first when creating a group #2575
Hi there, I am not sure if this is the right place to address the issue.
We are using the graph sdk to manage security groups. It worked well until as recently as this week. The issue that I am seeing now, is that the REST calls to create a group or delete a group seem exhibit async behaviour:
After creating a group with graphClient.groups().post(group);
I cannot immediately fetch it via graphClient.groups().byGroupId(created.getId()).get();
Instead I receive
...
Caused by: com.microsoft.graph.models.odataerrors.ODataError: Resource '7d97c410-af26-447c-81d8-....' does not exist or one of its queried reference-property objects are not present.
...
Also, the group with the respective ID is not listed when I access Entra via the web UI.
In the same way, a deletion of a group does not immediately produce an empty result when querying it via its ID.
When I wait some seconds, the GET request is successful and group is listed as usual in the web UI.
I am using the java SDK 6.62.0.
I cannot find breaking changes in the API changelog for Microsoft Graph.
changed the title [-]Async behaviour. "Resource does not exist" at first when creating a group[/-][+]Async behaviour: "Resource does not exist" at first when creating a group[/+]on Apr 21, 2026
Activity
[-]Async behaviour. "Resource does not exist" at first when creating a group[/-][+]Async behaviour: "Resource does not exist" at first when creating a group[/+]andrek-projekt commentedon Apr 24, 2026
Actually, it seems to be by design that Entra ID is eventually consistent:
https://devblogs.microsoft.com/identity/designing-for-eventual-consistency-for-microsoft-entra/?
I doubt that it be a good design though...