My Discord bot's auto-role setting said ON in 127 servers. It worked in 2.

The dashboard displayed the toggle in the "ON" position across 127 servers. The status command confirmed it was enabled. However, no member had received a role assignment. While working on a different task, I discovered this anomaly. A dashboard to-do item suggested auto-roles and a verification gate could both operate upon joining, potentially conflicting.

Before implementing the warning, I investigated their interaction. Auto-roles had no code path triggered during membership join. The member-join handler never processed them. The only location that granted auto-roles was the handler activated when a member successfully passed the verification gate. Consequently, the feature functioned exclusively in 2 guilds out of the 127 with auto-roles enabled and a role assigned.

The reason why no one noticed this anomaly lies in the consistent alignment of the settings page, status command, and the enabled status row. No aspect of the system verified whether a member ultimately acquired the role. An auto-role grant upon joining is simple to implement. The critical consideration arises when a gate is active.

A verification gate's purpose is to prevent members from receiving roles until they successfully complete the gate. Granting auto-roles upon joining would inadvertently negate the gate's intended function. Therefore, the join process checks the gate's enabled status and relinquishes control if the gate is active. The gate maintains sole authority over the roles.

The verification process employs the local flag rather than relying on the gate's outcome, as the gate call is irreversible and its result is not discernible from the join handler. If the two paths diverge, the member receives no roles. This approach is intentional: a missing role signifies a support message, while an incorrectly granted role denotes an incident.

The same planning function serves both the join path and a backfill for existing members, ensuring these paths remain consistent. The key takeaway from this incident is the importance of verifying the underlying premise of a bug report before commencing the fix. The specified conflict did not exist. The true bug stemmed from an omitted branch.

An enabled status in the settings merely confirms the row's existence, not the feature's execution. Testing the outcome is essential. When two paths have the potential to grant the same permission, it is crucial to determine which path should fail safely before implementing either. I am developing Akiko, a Discord bot featuring AI chat with memory capabilities, economy, music, moderation, and a web dashboard. It is available for free at https://i.hep.gg/akiko.