Unanswered

HTTP Request to Graph $expand Started to Fail

(3) Share

Report

Posted on by Ramtin S.

I have built a flow that updates a group of all managers in the organization every 3 hours. It uses an HTTP request to the Graph to list all users and expand their managers. However, this action started failing on Sep 22nd without any edits to the HTTP request. The error message says:

"Transitive manager's list is only supported on a single user, send the $expand request on /users/{id} endpoint."

The only way I could avoid the error was to set $top=1 and maximize the pagination threshold, but it slows down the action significantly, and I doubt it's the right approach.

Any ideas on how it started to fail suddenly and how to fix it?

Categories:

General topics

All responses (15)

Answers (0)

Sort by

vayinapurapu1 233 on at

Like
a
(0)

Report
Copy link

Link copied!

may i know the query that was working before? are you using V1.0 or beta?
microsoft-graph-docs/user-list-manager.md at main · microsoftgraph/microsoft-graph-docs · GitHub
Cheers,
Vinay.
henrip 12 on at

Like
a
(1)

Report
Copy link

Link copied!

I'm also seeing this error when querying Graph API for managers, the error first appeared on last friday 23/9/2022. The query I'm using is:
https://graph.microsoft.com/v1.0/users?`$expand=manager(`$levels=1;`$select=id)&`$filter=userType eq 'guest' and (endsWith(mail,'<domainname>') or endsWith(mail,'<domainname2>'))&`$Select=id&`$count=true&`$top=999

To me it seems that Microsoft has introduced changes to v1.0 that break existing functionality. Why even have versioning on the API in the first place if this kind of breaking changes are still beeing made to it? Querying user's manager one by one is not an option since the AAD tenant I'm working on has a large number of users.
Tomtom924S 19 on at

Like
a
(0)

Report
Copy link

Link copied!

Looks like it broke, I'm struggling with the same issue.. the following query worked just fine until yesterday, now it gives the same error..
https://graph.microsoft.com/v1.0/users?$top=999&$count=true&$filter=startswith(officeLocation,'US_')&$select=id&$expand=manager($select=id,mail,displayName,jobTitle;$levels=1 )
w0rdsm1th 9 on at

Like
a
(0)

Report
Copy link

Link copied!

+1 - this is also broken for me. My app needs to get all active user's managers from /users/ API so does not specify single user's id.

this $expand manager query was taken from Graph API docs. https://learn.microsoft.com/en-us/graph/api/user-list-manager?view=graph-rest-1.0&tabs=http#http-request
Expiscornovus 33,997 Most Valuable Professional on at

Like
a
(3)

Report
Copy link

Link copied!

Hi @w0rdsm1th,

In that article you are referring to there is actually a note about this in the optional query parameters section:

https://learn.microsoft.com/en-us/graph/api/user-list-manager?view=graph-rest-1.0&tabs=http#optional-query-parameters

$levels parameter is only supported on a single user (/users/{id} or me endpoints) and not on the entire list of users.
w0rdsm1th 9 on at

Like
a
(1)

Report
Copy link

Link copied!

ah thanks @Expiscornovus, I have tested and removing $levels gives me what I need. My query had $levels=1. I do agree with others tho, the API did definitely work specifying $levels and entire list of users before 23/9
henrip 12 on at

Like
a
(1)

Report
Copy link

Link copied!

Yes, this 100% was working with $levels=1 specified until 23/9. I've been running the same query as part of an automation for at least an year without any problems before.
Expiscornovus 33,997 Most Valuable Professional on at

Like
a
(2)

Report
Copy link

Link copied!

Hi @henrip,

I am not suggesting it was not working before 😁. Something definitely changed.

All I am saying is that the reason why it currently is not working is mentioned in the earlier shared Graph API documentation link.

FYI, the docs got adjusted back in July:

https://github.com/microsoftgraph/microsoft-graph-docs/commit/21d680e4b143550bc99f62a2e38b20e16037edd3
Tomtom924S 19 on at

Like
a
(0)

Report
Copy link

Link copied!

Right, it just stopped working. Removing $levels seems to solve it though, thank you! But I have been also able to filter for "officeLocation" with $count for months until 23/9, now that one gives an error too suddenly..
henrip 12 on at

Like
a
(0)

Report
Copy link

Link copied!

There is something weird going on with Graph API now. I just tried removing $levels and tested the query with Graph Explorer -> got "Transitive manager's list is only supported on a single user, send the $expand request on /users/{id} endpoint" -> kept hitting "Run query" again -> after 4 tries I got http 200 and the query worked as expected. So if you just keep querying with the same query approximately 1 out of 5 retries work and the other return http 400. Now also my original query with $levels is working intermittently.