Skip to main content
Skip table of contents

Batch Processing: Batch Status

Since the batch process is a long running and complex process, it may fail or terminate early due to server or database shutdowns or other problems. To avoid rerunning the whole batch or to recover from Configuration problems with Labels, parts of the batch process can be redone.

Since the Batch process may be run in the background, a temporary Status indicator may only mean the batch is still running.

If an error occurs you can use the application log to find details on the failure.

The following sections provide descriptions of the possible batch statuses.

Normal Status

  • Ready To Print: This indicates that the Create batch has been completed successfully and the batch is ready to be printed via the Process Batch Utility.

  • Printed: This status indicates that the Process Batch Utility has been run on this batch, and the user has marked the batch as printed.

  • BATCH NOT READY: Partial UnBatch Performed, Print Documents Need to be Rebuilt: When the Un-Batch method was run with a Filter, and Letters/Enclosures remain in the Batch, this status results. If the items removed from the original Batch fall within the filters specified on the new Batch, they are part of the next Batch.

Running Status or Abnormal Termination While Running

  • BATCH NOT READY: Prepping Letters: Some letters and enclosures were found to process, and the letter preparation function was about to be run. No letters or enclosures have yet been stamped with the new Batch ID.

  • BATCH NOT READY: Marking as Sent: The process to set the Batch ID and mark items as sent/picked has started but not completed. Each letter/enclosure set per Case is done as a Transaction and committed, so some may be marked and others not when termination happened.

  • BATCH NOT READY: Sending Email: All letter types specified as email are sent.  If this status remains after the batch terminated, it means some emails were sent and some not before the termination happened.

  • BATCH NOT READY: Creating Summary: all letters and enclosures have been marked as sent and have a batch ID (that did not have exceptions), and email have been sent. The process is now summing the counts to save for the Process Batch window to display.

  • BATCH NOT READY: Creating Print Documents: All the Print Documents (except for Labels) are being processed.

  • BATCH NOT READY: Creating Label Documents: the print documents related to labels and return labels are being created.

  • BATCH NOT READY: UnBatching: the Un-Batch method is in the process of removing the batch_id and marking letters as un-sent, and enclosures as un-picked.  They are committed on a case basis, so failure results in some of them remaining marked as sent and part of the batch.  Run Un-Batch again to complete the process.

Configuration or File Permit Error While Running

  • BATCH FAILED: Error Creating Print Documents: Some fatal error happened while creating the print documents for the batch.  The print documents are large appended sets of already prepared and stored letters.  Errors may be the result of running out of file space, or NT File directory permissions blocking the writing of the files.  Check the Application log for the specific problem.  To correct, Un-Batch the Batch, filtering emails as they have been sent.

  • BATCH FAILED: Error Creating Label Documents: a fatal or configuration error happened while creating the Label.htm or ReturnLabel.htm print documents for the batch.  This may be nothing more than a NULL value in a label field, which should not happen due to checks in early parts of the code, and to default values provided in the standard paragraph definitions.  To correct, Un-Batch the Batch, filtering emails as they have been sent.

  • BATCH NOT READY: Unknown/missing Status: X: The Batch ID is in an unknown state. It is possible that some internal error occurred while processing the batch.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.