The Team Tab of a Project is showing recent updates from a user who is no longer Active in CA PPM, in the field "Last Updated By."
They are originating from a user who has left the company, and whose user record is both Inactive and Locked.
The source of these updates is not known.
There are no Jobs against this user's name shown in the Job Logs.
This query enabled us to identify each time the issue occurred:
<Please see attached file for image>
The root cause is that a Job had become orphaned.
It was still running, but not visible through the user interface.
The root cause trigger is not known. It was investigated in detail from the backend of queries run, and a regular cause was not identified.
We theorise that a Job became stuck while the user status was changed while a Job was processing.
CA PPM 15.3 SAAS.
This has been addressed by:
1) Cleanly shutting down all known active Jobs.
2) Clearing all orphaned Jobs
3) Recycling the CA PPM Background Server.
These two documents were used as the reference source:
a) How to cleanup processes in Aborting State
b) CA PPM: Scheduled jobs stuck in waiting or scheduled status
If a CA PPM SaaS site encounters this issue, please contact CA Support to run the above procedures.
A CA PPM On-Premise site may run through the steps directly.
NOTE: Common, valid causes should be investigated and ruled out first. The most common is that when a user starts a Job, this is visible to themselves, but not to an Administrator looking into the general Job queue through the interface. You would need to log in as that user to see their Jobs. (Or else deep dive into running Jobs on a production system, which is not typically practical.)