Which statement is NOT true regarding Bulk Update of Advanced Workflow jobs?
A.
Bulk update jobs will automatically skip records enrolled in a workflow but already in an error state.
B.
If there are workflow jobs in progress, you will receive a warning which tells you how many jobs may be affected by this update.
C.
Only one update job can be run at the same time.
D.
Making changes to a workflow can make existing jobs fail.
The Answer Is:
A
Want to know why?
Explanation:
The Bulk Update Jobs feature is used to migrate active records from one version of an Advanced Workflow (AWF) to another. As taught in Advanced Workflow Beyond the Basics , Archer is designed to be cautious but thorough. Statement A is NOT true because the Bulk Update process actually attempts to evaluate all records targeted for migration. If a record is in an error state, the Bulk Update tool provides an opportunity to see if the new workflow version can resolve that state or if it remains "Incompatible."
Statements B, C, and D are all accurate reflections of the platform's behavior. Archer will indeed warn you about the volume of affected records (B), and the system enforces a "one-at-a-time" rule for Bulk Updates (C) to prevent database deadlocks and performance spikes. Furthermore, it is a known risk (D) that structural changes (like deleting a node where records currently reside) can cause those specific jobs to fail during or after an update. Therefore, administrators must use the "Compatibility" check within the Bulk Update interface to identify and resolve these issues before finalizing the migration.
