API doesn't publish updated timestamps for rescheduled event occurrences

[Reedbeta]

Description

Hello, I'm experiencing an issue with scheduled events using the Discord API. I'm observing that when a single instance of a recurring event is rescheduled, the start/end timestamps returned by the API for that occurrence do not update; the original start/end timestamps continue to be returned.

This doesn't happen with one-off events, only recurring ones.

As far as I can tell, there is no workaround, nor is there any way to identify for which events the API is serving wrong data.

Steps to Reproduce

Repro steps:

• create a recurring event in a server
• use API to fetch scheduled events (guild.scheduledEvents.fetch() in discord.js). Observe the event is returned with correct data.
• use the Discord client to change the date or time on the next instance of the recurring event
• use API to fetch scheduled events again. Observe that the event data returned is the same as before and has not updated with the new start/end timestamps.

Expected Behavior

Discord API should return correct and up-to-date properties of the event.

Current Behavior

Discord API continues to return the original start/end timestamp regardless of later changes to the event occurrence.

Screenshots/Videos

No response

Client and System Information

discord.js v14.17.2
Node v22.12.0
Windows 10 22H2

[advaith1]

Changes for specific occurrences are event exceptions, which aren't documented yet but there is a PR #8389

[Reedbeta]

Alright. It's great that there's work being done to expose recurrence exceptions, but I feel like that misses the point slightly.

AFAIU, the API publishes the next upcoming instance of a recurring event, as a regular scheduled event (with a recurrence rule attached), for the convenience of clients not having to handle recurrence logic themselves. But this event doesn't update to reflect edits to that next occurrence. I would like to see this fixed, independently of exposing new APIs for recurrence exceptions.

[advaith1]

The base scheduled event fields provide the standard template for the event. This behavior is intended and a change to that would be a breaking change. To find information for any specific occurrence of a recurring event, you must check the exceptions field.

[Reedbeta]

I see, thank you for the explanation. I'll look forward to the exceptions data becoming available.