Advanced Workflow Service Maintenance
This topic is only applicable to Archer on-premises installations.
The Advanced Workflow service administers the Archer Advanced Workflow feature, and must run constantly in environments that use workflows.
Tables within the Archer Instance Database support Advanced Workflow functionality. These tables contain metadata about workflow processes, and transactional details about enrolled content. Some of these tables accumulate large amounts of data, depending upon Advanced Workflow activity, and purge automatically after 30 days. Administrators can change the Advanced Workflow data retention period.
Initiating data feed or data import actions for applications enabled for Advanced Workflow can cause the Advanced Workflow transaction tables to rapidly accumulate data. In these cases, disable the target application’s Advanced Workflow process before a bulk data action, and re-enable it upon completion.
Performance Analysis Notes for Advanced Workflow Bulk Data Actions
- Testing produced the following results in an environment with 1 web server and 1 database server, each running Windows Server 2012 R2 with 8 CPUs and 48GB RAM.
- Archer processes AWF bulk data actions at a rate of approximately 1000 records per minute.
- Average CPU utilization on both servers averages 5% while a bulk action job runs.
- Memory utilization on both servers is insignificant.
- Performance metrics are similar whether records wait on a User Action Node or a Wait For Content Update Node while a bulk action job runs.
