GitLab is introducing changes to improve the reliability and reduce manual intervention of webhooks, which will affect GitLab.com users in the coming weeks. The changes will also be available for GitLab Self-managed users behind an existing ops flag. The update allows all webhooks to self-heal, regardless of the error type, and temporarily disables failing webhooks instead of permanently disabling them. This change treats all types of errors consistently, making behavior more predictable and easier to troubleshoot. The update reduces manual intervention, improves reliability, and better handles temporary issues. Users should review their webhooks, prepare for reactivation, ensure their systems can handle webhook events, and update their monitoring. The feature will be rolled out over two weeks to ensure a smooth transition. For GitLab.com users, the changes will be applied automatically, while for self-managed and Dedicated users, the changes will only affect instances with the auto_disabling_webhooks ops flag enabled from Version 17.7. Users can provide feedback on the webhook feedback issue and reach out to GitLab Support or consult the webhooks documentation for any questions or concerns. The update is the result of a valuable community contribution, demonstrating the power of the open source community in driving GitLab forward.