Document Scheduled Event Exceptions #8069
Open
+175
−35
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Droid00000
force-pushed
the
feat/scheduled-event-exceptions
branch
from
7df366f to
a31fcbd
Compare
valzargaming
reviewed
Jan 9, 2026
Droid00000
force-pushed
the
feat/scheduled-event-exceptions
branch
from
f686f96 to
47961ec
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This feature has a few interesting things to note:
Updating a pre-exisiting exception fires a
GUILD_SCHEDULED_EVENT_EXCEPTION_CREATEinstead of an update.Removing the
recurrence_rulefor a scheduled event that already has exceptions doesn't remove any of the existing exceptions.There is a seemingly unused
GUILD_SCHEDULED_EVENT_EXCEPTIONS_DELETEevent that exists. I tried to see when it would fire, but even after setting therecurrence_rulefield tonullI still couldn't get it to fire.