Batch errors of various kinds are difficult to debug without a detailed record of what was going on at the time.
Batch creates a log file of all the significant events. You can find it in the TEMP folder (just type %temp% in the top bar of any File Explorer window). There may be more than one log file; the basic name is GH.BatchFramework.Client.log but there may be more than one log with unique numbers at the end of the name, like this:
Bladed support staff will normally request this log file to be sent whenever a Batch error is reported that can't immediately be solved. As there may be multiple files, it is important to send the one that covers the timespan of the problem occurring, as well as the Batch startup which is often a stage when problems show themselves. So to this end we recommend you to close Batch down, (using the System Tray icon, just right-click and Exit), then restart it. Restart either by typing "Batch" in the Windows Start menu box and hit Enter when Batch appears in the application list, or run a simulation in Batch from the Bladed GUI. Then carry out whatever steps are needed reproduce the error and locate the log file that covers the whole sequence of startup and error occurrence. (To confirrm this, you can open up a log file in any text editor and just look at the event timestamps).
You may need to gather log files from more than one machine in some instances, e.g. where it's not clear if the problem is with the manager or runner.