The issue is with Solidcore Rules, Installers. When a new installer is added, you can define both SHA-1 and SHA-256, only SHA-1, or only SHA-256. Currently, SHA-1 is always required because it has a unique constraint on SQL.
The procedure that inserts a value into the database checks if SHA-1 exists. If it exists, the other values are
updated using the same SHA-1, because it's unique. If SHA-1
does not exist,
all values are inserted. So, if a new installer is created without SHA-1, it's inserted with an empty value under SHA-1 the first time. The second time, it's not inserted. Instead, the previous value with no SHA-1 is updated, the task fails, and all rule groups are deleted.
NOTE: Run Rule Group Sanity Check
only if all installers have SHA-1. This task doesn't have to be run after every upgrade; it's optional to fix the inconsistencies in the rule group.