|Applies To||RSA Product Set: Archer|
RSA Product/Service Type: Archer
RSA Version/Condition: 5.x, 6.x
|Issue||Active campaigns create thousands of RecurringCampaignGenerationJobHandler jobs and back up the job processing within Archer.|
|Cause||If you have a re-occurring campaign job on a questionnaire, this issue can occur. It allows for nearly real-time generation of questionnaires based on the target application criteria. Every time a record is modified in an application which is a questionnaire target and that questionnaire is part of a campaign, a RecurringCampaignGenerationJobHandler job gets created to check the criteria to see if a questionnaire record needs to be created. This can greatly back up the system, especially when records are touched in mass by things like data feeds, calculations, and package installs where calculations are triggered. |
- Make sure that only current campaigns are active. Inactivate any campaigns that are for future use like yearly, quarterly, etc. Activate them only when it is time to use them. This will avoid having excess jobs backing up other jobs. To help identify active jobs, download the latest Job Info Script from https://community.rsa.com/docs/DOC-100403. You will need to filter jobs containing campaign and @CampaignDetails BIT = 1.
- Reduce the number of updates to the records such as data feeds, package installs and/or calculations on the records. If you have calculations with TODAY() or NOW() and always calculation then those are more likely to trigger updates to the record and generate a campaign job for each record.
- Add filters in the Job Engine Manager within the Archer Control Panel to ensure that high priority jobs are processed first.
- Increase the amount of Job Engine Servers/threads so that the number of jobs can be processed in a timely manner.