Workflow History should be purged. Not purging leads to slow performance and eventually lack of disk space as each workflow generates 100+ records across multiple tables. Oracle provides a general program to purge workflow history and a special one just for Order Management workflows. But for many companies these purge programs still leave hundreds or thousands of workflows in the tables. This presentation explains why the seeded programs won’t purge all history and provides some tips and techniques to resolve the issues thus reducing your workflow history footprint and some cautions to ensure that catching up on your purging doesn’t cause performance issues or purge approval history required by audit.