This article was created as a Master Article for all things Locked Payment Batches within Munis. Batches can get locked for a few different reasons including multiple users attempting to make changes in the same batch or with two different programs, server connectivity issues and even users clicking the browser (X) to close out of Munis programs instead of Munis' built in Back button which allows processing to finish before closing out properly. There are also times where users might might be selecting all of the batches for posting in a program like Payments Journal and this can erroneously lock the batch for posting by that user. There are also times where sites may see a ' POST_IN_PROGRESS ' message related to one or more batches after a failed posting which these are due to server to Munis connectivity or users hard closing out of Payments Journal before the posting finishes either from Munis, Chrome or other supported browser. Munis will lock the batch and populate the clerks name as ' (*POST_IN_PROGRESS*)'. See resolutions below to assist in unlocking batches in the respective version and scenario. |