Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2021 Release Wave 1Discover the latest updates and new features to Dynamics 365 planned April 2021 through September 2021.
Release overview guides and videos Release Plan | Preview 2021 Release Wave 1 Timeline
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
I've deleted all "System Jobs" in an environment regardless of their "Status". However, 4 days have passed and the WorkflowLogBase is still taking up 200GB. Any idea why the database is still so large and how I can fix it?
Hope you are doing wonderful.
Am sure you must have followed this script to clean up the WorkflowLogBase and AsyncOperationBase:-
If the same script has been applied and the size is still taking huge, please check the size of AsyncOperationBase table as well?
Also check how many processes/workflows must have been executed in the last 4 days?
The logs created in 4 days are relevant async job created or any duplicates? verify the table records and confirm the same.
Please keep us posted with more details.
Business Applications communities