Bot would not enter scan in AltR2E1

[late dock]

SORRY NO FOOTAGE

We were just playing AltR2E1 with 2 other friends (3 players total) + 1 bot. We failed and died because the bot would not enter the final scan of the 2nd surge alarm (Class IV surge in Zone 597). We tried to ask him to follow us so that he would move and enter the scan, but he stayed just outside the scan and refused to enter.
We thought it might be because the final scan was located inside one of the concrete tunnel structures, or because of a slight elevation change due to terrain roughness.
This is the first time in 200h that this has happened to us, and we are very afraid that it might happen again later in the level and be very frustrating.
Any input on this issue would be really appreciated.

[gaunt pond]

I can confirm, I was there

[split sphinx]

This is a known bug since bots were added but there have been quite a few reports of it happening more recently.

Sometimes the pathfinding AI simply bugs out on the bot and it acts like it DOESN'T want to enter the scan for some reason. There are a couple of fixes but none of them are convenient unfortunately.

Easiest fix is to have the host override the bot slot to "players only" by hitting ESC and changing the slot and then changing it back to "bots only".

Naturally this bug is very problematic during a hectic alarm, but the best I can offer is that you immediately boot the bot as soon as you notice it in order to refresh the AI.

Otherwise you can boot the bot until the full team portion of the scan is completed and then add it again to be completely certain.