Batch Service Manager server options

The

FactoryTalk Batch

Server starts in a new instance without restoring data from its previous run. Batches are not added back to the batch list, and operator arbitration states are not recovered. For all batches that were not restored, batch completion events are recorded in the

FactoryTalk Batch

Event Journals. After a Cold Restart, you will not be able to resume execution of batches from the previous instance. If Security Authority is enabled, SAIs in a secured area model and any secured recipes must match the current Network FactoryTalk Directory SAI.

Restarts the

FactoryTalk Batch

Server and attempts to restore the set of batches that were on the batch list when the server previously stopped. Batch complete events are added to the

FactoryTalk Batch

Event Journals for all batches that were not restored to the batch list. After a Warm Restart, any batches that are not restored cannot be recovered or resumed in the future. Batches are restored in Manual execution mode with active transitions in a HELD state. No validation for Security Authority is performed.

The

FactoryTalk Batch

server attempts to restart but will not restart if it is unable to restore all the batches to the batch list. If a Warm All Restart attempt fails, the ability to restore batches in the future is not affected. After the issues are resolved, another attempt to restore the batches to the batch list can be made using Warm Restart, Warm All Restart, or Hot Restart. This is the default setting for automatic restarts. Batches are restored in Manual execution mode with active transitions in a HELD state. No validation for Security Authority is performed.

Follows all the startup rules of Warm All Restart. In addition, the

FactoryTalk Batch

Server attempts to restore batches to their last known state, including transition states and recipe modes, without any operator interaction.