Status(Install_Status) of Cloud Resource CIs is showing as "Updated by" individual users due to the "Run As" user being set to the creator of the Cloud Discovery Scheduled JobIssue Status(Install_Status) of Cloud Resource CIs is showing as “Updated by” individual users due to the “Run As” user being set to the creator of the Cloud Discovery Scheduled JobReleaseWashington DC CauseThe following is the root cause for the updates to Cloud CIs being made by individual users due to the Cloud Discovery Schedule Job “Run As” being incorrectly set.This is happening at the time of Cloud Discovery Scheduled Job creation. When a Cloud Discovery Scheduled Job is triggered, the following is happening: 1.The Cloud Discovery Schedule Job is created with the “Run As” as the username of the person who created the Scheduled Job. So when the Scheduled Job is run, it creates a Discovery Status under the same “Run As” username as the Cloud Discovery Scheduled Job. 2.The Cloud Discovery uses the appropriate patterns to discover the Service Account and LDCs configured in the Scheduled Job. The Discovery Status references each of the LDCs that are configured under the Service Account and updates the Discovery Status to show this.3.The appropriate Patterns are launched to discover the Cloud Resources.-The Cloud Resource CI updates happen during Step 2 where the transaction is running under the “Run As” username that the Cloud Discovery Scheduled Job was created with. -In the reported issue, the LDC has an Status(Install_Status) of “Retired” so whenever the LDC is updated by a new Discovery Status it triggers the “Cascade Update LDCs Resource State” Business Rule, which updates all Cloud Resources hosted on the LDC to Status(Install_Status) = “Retired” as well. Since the updates occur under the Cloud Discovery Schedule Job that has the “Run As” username set to the name of the person who created the Schedule Job, the “Updated By” user gets listed as the same username.Resolution1.When creating Cloud Discovery Scheduled Jobs, it is a best practice to change the “Run As” to a username other than the username of the individual who created the job, such as a system account. 2.Research needs to be done to ensure that LDCs associated with active Service Accounts are listed as Operational Status of “Operational” and Status(Install_Status) of “Installed” instead of “Retired.