2026-01-23: Groups on gitlab.com cannot update settings due to timeout
Groups on gitlab.com cannot update settings due to timeout (Severity 2)
Problem: Users are unable to update Duo settings for groups on gitlab.com due to request timeouts.
Impact: Users cannot update Duo settings for groups on gitlab.com through the UI. There is no workaround for updating Duo access rules, DAP/flows/agents, or prompt caching, as these updates always time out. Customers can update the 'duo_availability' attribute via the Groups API as a partial workaround, but key settings remain inaccessible. Affected users see 500 errors when attempting updates.
Causes: A recent code change introduced an expensive Redis scan triggered by a cache clear in the UI when updating Duo settings for groups, causing update requests to time out.
Response strategy: We merged a revert for the problematic code change and set up a manual deployment pipeline to bypass weekend release restrictions. Release to production has completed successfully and manual testing has confirmed that Duo settings can now be updated as normal for all users.
This ticket was created to track INC-6797, by incident.io