Inconveniences at adding git roots in a group
Incident Report for Fluid Attacks


At least one group experienced problems adding new git roots via ZTNA into the Scope section of the Platform (at UTC-5 22-09-13 15:28 to 23-11-20 09:30 | Time to recover was 3.7 days). The incident was reported proactively (at UTC-5 23-11-16 16:43 | Time to detect was 14.1 Months) through our help desk [1] by a member of the experience team, who was setting up a PoC.


The problem originated during a migration, not considering inactive elements within the organization due to group deletion. The migration focused only on active group elements, leaving out the roots of the deleted groups. As a result, these group roots missed out on receiving the new attributes [2].


The team performed a new migration to add the missing data to the incomplete git roots [3].


Currently, there is no way to test this type of migration to ensure the completeness of the data, becoming prone to overlooking crucial elements, as observed in this instance. The team is working on new strategies to guarantee the integrity of the data after any migration to avoid these issues. DATA_QUALITY < FAILED_MIGRATION < MISSIGN_TEST

Posted Nov 20, 2023 - 13:42 GMT-05:00

The incident has been resolved, and now the addition of git roots works correctly.
Posted Nov 20, 2023 - 12:26 GMT-05:00
Some problems were noticed when trying to add git roots to some groups via ZTNA.
Posted Nov 17, 2023 - 11:15 GMT-05:00
This incident affected: Platform.