Observations from endpoints are initially entered in this table, an internal ePO task runs every few minutes to process the observations, they are then deleted from the table. When the scor_async_job table gets too large the task does not have time to finish and never deletes the rows. You will also see very high traffic on the network between ePO and the SQL server when this is happening too.
I've seen this after an agent handler crash that went unnoticed. The solution in my case was to delete all rows in the table to allow the task to get on top of things.
Create a support ticket and confirm with them the correct action, they will provide the SQL to run to clear the table.
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.
Community Help Hub
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.