Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fail to create shared channels #852

Open
shani-hollander-hs opened this issue Aug 7, 2024 · 1 comment
Open

Fail to create shared channels #852

shani-hollander-hs opened this issue Aug 7, 2024 · 1 comment
Assignees
Labels
area: API Support Focused on MS Graph API itself type:bug A broken experience

Comments

@shani-hollander-hs
Copy link

Describe the bug

When sending requests for channel creation with a membershipType value of shared, we get a 202 Accepted response code.
The channels are not getting created after long periods of times (hours) or not getting created at all

This has been happening for the last 24~ hours, and is a new error

Expected behavior

Channel of type shared should be created in a matter of seconds/minutes after getting 202 response

How to reproduce

Create a channel with a membershipType value of shared -


request_body = Channel(
	display_name = "Architecture Discussion",
	description = "This channel is where we debate all future architecture plans",
	membership_type = ChannelMembershipType.Shared,
)

result = await graph_client.teams.by_team_id('team-id').channels.post(request_body)

SDK Version

No response

Latest version known to work for scenario above?

No response

Known Workarounds

No response

Debug output

Click to expand log ```
</details>


### Configuration

_No response_

### Other information

_No response_
@shani-hollander-hs shani-hollander-hs added status:waiting-for-triage An issue that is yet to be reviewed or assigned type:bug A broken experience labels Aug 7, 2024
@shemogumbe
Copy link
Collaborator

Hello @shani-hollander-hs thanks for using the SDK and for reporting this.

From your issue, looks like this was working and just recently stopped working, however, considering that you are receiving 202 statuses in the response, this could be related to the service.

Could be helpful to log a ticket here

@shemogumbe shemogumbe added area: API Support Focused on MS Graph API itself and removed status:waiting-for-triage An issue that is yet to be reviewed or assigned labels Aug 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: API Support Focused on MS Graph API itself type:bug A broken experience
Projects
None yet
Development

No branches or pull requests

2 participants