question

IanSimpson-4486 avatar image
0 Votes"
IanSimpson-4486 asked IanSimpson-4486 commented

Random Bad Request and Forbidden responses from certain endpoints

I've started getting seemingly random Bad Request and Forbidden responses from Graph. The overall execution of the code does the following:
1) Create a MS Teams Team be calling POST - https://graph.microsoft.com/v1.0/teams
2) Add guests to that Team
3) Create folders for all guests under the main channel
4) Remove all permissions from folders (aside from "owner" role) and re-add the appropriate guest as the manager of that folder
5) Create a meeting related to the created Team.

Everything was working fine until today.
1) I started getting Forbidden responses from POST - groups/{team-id}/events. This was fixed by tweaking the date format. But then
2) I started getting Bad Request or Forbidden responses from DELETE - groups/{team-id}/drive/items/{item-id}/permissions/{permission-id}
3) I also began getting Forbidden responses from POST teams/{team-id}/members

These errors are all random. Sometimes I'll get lucky and the request will go through with identical parameters. Error 3 appears to go away if I manually get a new OAuth token before trying the request.

office-teams-app-devmicrosoft-graph-teamwork
· 8
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Adding right tags/teams to assist.

0 Votes 0 ·

Hi @IanSimpson-4486, we are working on it , will update you soon.

0 Votes 0 ·

Hi @IanSimpson-4486, We are unable to reproduce the issue, are you still facing the issue. If yes, could you please try again once.

0 Votes 0 ·

Hi @IanSimpson-4486, could you please le us know if you are you still facing the issue.

0 Votes 0 ·

Yes this is still an issue. See this SO post: https://stackoverflow.com/questions/67077990/should-i-have-to-wait-after-creating-team-with-graph

Note that both answers indicate they are able to see the issue.

0 Votes 0 ·

Hi @IanSimpson-4486, is your issue not sorted even after implementing those two resolutions from the stack overflow. Please let us know , so that we can raise a bug for this.

0 Votes 0 ·
IanSimpson-4486 avatar image IanSimpson-4486 JagadeeshLankiReddy-5847 ·

Those two "resolutions" are work arounds that I may be trying soon, although they are not substantively different than just waiting a minute or two. An actual solution would be to give an indicator of when a Team is actually ready to use in the API instead of trying different API requests and seeing if they return 404. Not to mention that the forbidden response sometimes sent is an outright bug, because the indication from that response is completely wrong.

0 Votes 0 ·
Show more comments

1 Answer

JagadeeshLankiReddy-5847 avatar image
0 Votes"
JagadeeshLankiReddy-5847 answered IanSimpson-4486 commented

Hi @IanSimpson-4486, we have created bug for this , our engineering team is working on it . We don't have any ETA to share with you on fix.

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Thanks Jagadeesh

0 Votes 0 ·