Hardening a Bot for 24/7 Operation

A music bot that dies at 8 PM on a Friday might as well not exist. The classic failure modes are all memory leaks and listener leaks — and they're all handled deliberately in SYN MUSIC.

Search pickers and queue pages expire after five minutes. Leaving or kicking a guild releases its player, timers and votes instantly through GuildDelete cleanup. The settings cache is a bounded LRU capped at 1000 guilds. Nothing grows unbounded.

The music manager is a true singleton with a client-level guard, so hot-reloads can't double-register voice or guild events or arm two now-playing timers. Command gates share a single cached settings fetch instead of several database round-trips.

Embed edits are throttled to every 2.5 seconds — and only when progress actually moved — so a busy bot never spams the REST API. History and stats writes are fire-and-forget.

And when things do go wrong, the bot heals itself: a dead-player watchdog, retry-once track faults, position-based end detection as a fallback, stream auto-reconnect and resume, and graceful shutdown that flushes state cleanly.