Resolved -
This incident has been resolved.
May 13, 21:39 UTC
Monitoring -
Fixes have been implemented and I am now monitoring the results.
Serenity is online and fully functional as it stands.
May 13, 21:26 UTC
Identified -
I have identified 5 key runtime issues and have implemented fixes:
• Webhook 404s: Handled gracefully and removed invalid webhooks from DB.
• Null .id access: Added safe checks to prevent crashes.
• Unknown interaction (10062): Used deferReply() to avoid Discord timeouts.
• Max pinned threads (30047): Skips pinning if limit is reached.
• Missing permissions (50013): Silently skips blocked actions to avoid crashes.
I will deploy these changes shortly and perform a restart on Serenity.
May 13, 21:18 UTC
Investigating -
We are currently experiencing unexpected downtime across the Serenity Bot due to a series of backend and API-related errors, including Discord integration issues and permission-related failures.
I am actively investigating the cause of these errors, including verifying Discord API states, checking permission scopes, and reviewing the current thread/pin limits within affected channels.
I sincerely appreciate your patience during this time and will post updates as we bring Serenity back online.
May 13, 20:39 UTC