Dynamics Community Forum Thread Details

Deleting Failed AsyncOperations

I got a set of system jobs that are locked in 'In Progress'.

After investigation, I found article that refer the issue to "AsyncOperationBase table’s size" may make CRM asynchronous services can begin to show signs of degradation.

according to MS article there

https://support.microsoft.com/en-us/help/968520/performance-is-slow-if-the-asyncoperationbase-table-becomes-too-large

it's recommended to do the following

Make sure that only the following Async operation types are deleted if the state code of the types is 3 and the status code of the types is 30 or 32:

Workflow Expansion Task (1)
Collect SQM data (9)
PersistMatchCode (12)
FullTextCatalogIndex (25)
UpdateContractStates (27)
Workflow (10)

After making queries on the Asyncoperation table I found out that only rows count of OperationType = Workflow (10) and status code = failed (31)

exceeds 1,2 Million records considering that total records of Asyncoperation table is 2.5 Million records .

as a result, I see that I should include the failed jobs into this query

"Make sure that only the following Async operation types are deleted if the state code of the types is 3 and the status code of the types is 30 or 32"

to be

Make sure that only the following Async operation types are deleted if the state code of the types is 3 and the status code of the types is 30 or 31 or 32 "

I want to know :-

- Does deleting failed system jobs from Asyncoperation table have any bad impact on the system ?

- Is there any alternative method to delete those jobs using CRM UI "Bulk Delete jobs" instead of running SQL queries on database

Regards

Hy Partner,

Hope this post finds you well.

When you want to clear a large number from AsyncOperationBase table, make sure you do in off business hours. It will help platform to accommodate all resources of async service to do this operation. In addition to it, if possible pause all other data management jobs and let this be cleared.

Deleting failed system jobs won't have bad impact on the system, but if number is huge , you need to take care as it should not be done in business hours, as it might impact the performance of the system.

It can also be deleted through Bulk Delete Records jobs. You can schedule a job choosing system job as an entity and provide the filter criteria for the same and proceed.

Hope this helps.

Best regards,

Ankit

Please mark as verified if the answer is helpful. Welcome to join hot discussions in Dynamics 365 Forums.

Quick Links