Reasons to Batch going into offline status

When a batch is inaccessible, it immediately is placed into offline status by a client. Ensure that:

1. The batch directory exists at the listed folder path

-- Click or double-click on batch ID in Job Monitor for this value

2. The Windows user has sufficient privileges to the batch directory

3. There are no network issues from the client PC to the server

Once these have been confirmed, simply rollback the batch to "pending" or "hold" status and reprocess.

Note: Network logs should be audited around the times batches are run and placed into "offline" status if the issue becomes problematic.