Teams Recurring Meeting Update Issue with Graph API
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- node.js, typescript
- Domain
- api
Research direction
Start with the Microsoft Graph /me/events endpoint and the PATCH URL construction shown in the Node.js snippet, comparing eventId with instanceId. Reproduce the sequence of updating the series, updating one recurring instance, and updating the series again. Done would require identifying the source of the 500 response and documenting or confirming the supported update behavior; no repository file or test is mentioned.
Written by the indexing model from the issue text.
Description
I successfully created a recurring Teams meeting using the Graph API.
After that, I updated the entire recurring series using the Graph API, which worked successfully.
I then tried updating a single instance of the recurring series using the Graph API, and that also succeeded.
However, once I update any single instance of the recurring series, any subsequent attempt to update the entire recurring series results in a 500 Internal Server Error from the Graph API.
Below is the code snippet I’m using to update the meeting in Node.js:
process.env.teamsScheduleMeeting = "https://graph.microsoft.com/v1.0/me/events"
const headers = {
'Authorization': `Bearer ${token}`,
'Content-Type': 'application/json',
'Prefer': `outlook.timezone="${payload?.timezone ? payload?.timezone : payload.booking.timezone}", outlook.body-content-type="text"`
};
const meetingData = {
...(payload?.title && { subject: payload?.title }),
...(payload?.startTime && payload?.endTime && payload?.timezone && {
start: {
dateTime: new Date(Number(payload?.startTime)).toISOString(),
timeZone: payload?.timezone
},
end: {
dateTime: new Date(Number(payload?.endTime)).toISOString(),
timeZone: payload?.timezone
}
}),
...(payload?.recurrence && { recurrence: payload.recurrence }),
...(payload?.participants && Array.isArray(payload?.participants) && {
attendees: payload.participants.map(email => ({ emailAddress: { address: email } }))
})
};
const teamsMeetingUpdateUrl = `${process.env.teamsScheduleMeeting}/${payload.type === "recurringInstance" ? payload.instanceId : payload.eventId}`;
const existingEventDetails = await axios.get(teamsMeetingUpdateUrl, { headers });
const existingContent = existingEventDetails?.data?.body?.content;
if (payload?.description) {
// Update the body content only if a new description is provided
meetingData.body = {
contentType: 'text', // Retain original or default to text
content: existingContent.replace(/^(.*?)(\r\n|$)/, `${payload.description}$2`) // Replace first line with the new description
};
}
const updateEvent = await axios.patch(teamsMeetingUpdateUrl, meetingData, { headers });
console.log('updateEvent---', updateEvent);
Can some one help me understand why the Graph API fails with a 500 error when updating the entire series after modifying a single instance?
- Dominant language
- TypeScript
- Stars
- 833
- Forks
- 240
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoftgraph/msgraph-sdk-javascript
-
status:waiting-for-triage
Difficulty 1/5 Under an hour Newbie friendliness 62/100
-
Is anyone here? Open
Difficulty 4/5 3-5 days Newbie friendliness 25/100
microsoftgraph/msgraph-sdk-javascript#2005 · 1 reaction ·
-
Is it really correct that the Javascript version of the graph SDK doesn't offer typed requests? Openstatus:waiting-for-triage
Difficulty 5/5 Over a week Newbie friendliness 42/100
-
status:waiting-for-triage type:bug
Difficulty 3/5 1-2 days Newbie friendliness 48/100
microsoftgraph/msgraph-sdk-javascript#1999 · 2 comments · 1 reaction ·
-
status:waiting-for-triage type:bug
Difficulty 4/5 3-5 days Newbie friendliness 45/100