At least one root encountered an error message when attempting to switch from Legacy VPN to Secure Access. The issue started on UTC-5 23-05-25 15:00 and was reactively discovered 3.7 months (TTD) later by a user who reported it to one of our engagement managers [1] that he encountered an on-screen error message There is an error :(. The problem was resolved in 3.3 days (TTF) resulting in a total impact of 3.8 months (TTR).
The mutation responsible for transitioning from Legacy VPN to Secure Access, identified by the name updateGitRoot, relies on a field named organization_name, which must be present in each vulnerability. However, the issue arose because at least five vulnerabilities lacked this field due to an oversight during data population via migration [2].
A migration was executed to populate the organization_name field in all vulnerabilities where it was absent.
The issue stemmed from the absence of a required field in the vulnerabilities, resulting from an oversight during migration. DATA_QUALITY < FAILED_MIGRATION