Stuck at [INFO.BargeMinerV2] Attempting mining cycle.

Hi, just managed to get the bot running for the first time by docking it to a station in the same area I want to mine and starting the bot, all goes well until the belt is done.
Mining with a procurer, once the belt is done bot gets stuck at this stage and doesn't proceed...
Any suggestions?

{
  "InstanceName": "default",
  "ADBPath": "",
  "ADBSocket": "127.0.0.1:5037",
  "ADBDeviceName": "default",
  "ADBInstancePort": 0,
  "DeviceID": 0,
  "CloneID": 1,
  "Mode": 2,
  "ContrastAdjustment": {
    "Enable": false,
    "Percentage": 10
  },
  "ConnectToGCS": false,
  "GroundControlSocket": "127.0.0.1:9000",
  "PVEAssist": false,
  "Venture": false,
  "Verbosity": 1,
  "Killswich": true,
  "RandomizeInput": true,
  "RandomizationOffset": {
    "min": 0,
    "max": 7
  },
  "SendStats": true,
  "SaveStats": true,
  "BeltsClusterPriority": 0,
  "Miners": null,
  "Strip_Miners": null,
  "Stabs": null,
  "OverrideHomeStation": {
    "X": -1,
    "Y": -1
  },
  "Timings": {
    "AlignTime": 5,
    "WarpTime": 10
  },
  "Session": null,
  "MainScript": "main.lua",
  "RedScanSensitivity": 0.97,
  "DoubleCheckRedScan": false,
  "ScanLocalInBelt": false,
  "ScanBeforeUndock": false,
  "ScanDelayAfterRecall": 3,
  "SendRedNotification": true,
  "SendFullLocalScreenshot": false,
  "SendDumpNotification": true,
  "OnlyApproachAsteroids": false,
  "SendRedNotificationDelay": 2,
  "RescanDelayAfterGCSRecall": 2,
  "WatchDogMode": false,
  "OresToMine": [
    14,
    5,
    15,
    3,
    8,
    1
  ]
}

---

If I warp the bot to the next cluster/belt it resumes mining just fine, so it's missing a trigger to identify when the belt is consumed so it can move on

Hi, just managed to get the bot running for the first time by docking it to a station in the same area I want to mine and starting the bot, all goes well until the belt is done.
Mining with a procurer, once the belt is done bot gets stuck at this stage and doesn't proceed...
Any suggestions?

{
  "InstanceName": "default",
  "ADBPath": "",
  "ADBSocket": "127.0.0.1:5037",
  "ADBDeviceName": "default",
  "ADBInstancePort": 0,
  "DeviceID": 0,
  "CloneID": 1,
  "Mode": 2,
  "ContrastAdjustment": {
    "Enable": false,
    "Percentage": 10
  },
  "ConnectToGCS": false,
  "GroundControlSocket": "127.0.0.1:9000",
  "PVEAssist": false,
  "Venture": false,
  "Verbosity": 1,
  "Killswich": true,
  "RandomizeInput": true,
  "RandomizationOffset": {
    "min": 0,
    "max": 7
  },
  "SendStats": true,
  "SaveStats": true,
  "BeltsClusterPriority": 0,
  "Miners": null,
  "Strip_Miners": null,
  "Stabs": null,
  "OverrideHomeStation": {
    "X": -1,
    "Y": -1
  },
  "Timings": {
    "AlignTime": 5,
    "WarpTime": 10
  },
  "Session": null,
  "MainScript": "main.lua",
  "RedScanSensitivity": 0.97,
  "DoubleCheckRedScan": false,
  "ScanLocalInBelt": false,
  "ScanBeforeUndock": false,
  "ScanDelayAfterRecall": 3,
  "SendRedNotification": true,
  "SendFullLocalScreenshot": false,
  "SendDumpNotification": true,
  "OnlyApproachAsteroids": false,
  "SendRedNotificationDelay": 2,
  "RescanDelayAfterGCSRecall": 2,
  "WatchDogMode": false,
  "OresToMine": [
    14,
    5,
    15,
    3,
    8,
    1
  ]
}

---

If I warp the bot to the next cluster/belt it resumes mining just fine, so it's missing a trigger to identify when the belt is consumed so it can move on

Can you set "Verbosity": 3? So you can have the full log. Also check for ingame resolution to be 100%.