Older,Same batch is displayed in a Taskmaster Web session in Datacap

When trying to run a shortcut or batch in Taskmaster Web, a previously worked batch is displayed to the operator

Signs:

An operator clicks on an Operations shortcut link or attempts to run a batch manually through the Job Monitor, but the batch attempting to be selected is not displayed; instead a batch that was previously worked on by the user during his or her Taskmaster Web session is brought up.

Note: These symptoms occur even if Taskmaster Web (IIS) and Internet browser settings are configured to not cache pages, and even when bypassing the load balancer if one is applicable to the environment.

Reason:

If an operator starts a batch but does not finish it correctly, then this behavior will occur. That is to say, the operator did not cancel the batch, place it on hold, or submit/finish it. In many cases the user may have navigated away from the batch using the Internet browser's navigation buttons rather than the Taskmaster Web content buttons.

Solution:

This feature is by design for data integrity reasons. To avoid these symptoms or resolve them when they occur, the operator should use the appropriate Taskmaster Web buttons to release the original batch per normal processing. For example, in Verify the operator should index and Submit all pages or place the batch on hold. Once the batch has been processed and released per normal business procedures, the user will be able to move on to any other batch.