GRC Entity Records Have Been InactivatedIssue Some Scoped Entities are getting deactivated by the system, despite the GRC admin reactivating the entity manually. The scheduled job: 'GRC Cleanup Invalid Profiles and entity type' inactivates the entity daily. We can see entity records are inactivated once the applies_to CI has been reclassified.ReleaseQ1 2025 release of GRC: ProfilesCauseI've confirmed from my employee sandbox instance that when the applies_to record has been reclassified there is no updated to the sn_grc_profile to have it reflect the CI's latest class. The scheduled job: 'GRC Cleanup Invalid Profiles and entity type' will then check if the sn_grc_profile.applies_to record still exists on the sn_grc_profile.table, and when not found inactivate the entity. This job is leveraging the function GRCUtilsBase.inactiveInvalidProfiles()ResolutionThe solution proposed is to create a custom business rule on the cmdb_ci table to perform the roll-up logic. There is currently no intention listed on the product roadmap to have this included as a baseline feature. An enhancement request can be created in ServiceNow's idea portal if this is something that needs to be pursued further.