This bug doesn't happen on every match, but in the matches it happens in, it always happens. I have an AI that uses tags for calling "dibs" on resources so they all get picked up faster. I even go so far as to make a brigade, so that faster bots can trade with slower bots. It doesn't look like the tag update caused this, but I can't say that for certain. I do know this didn't happen before Alpha 12.
Here's a snapshot before the bug, everything is working fine, the machine gun is trying to capture the A resource in short range (in this AI, only machine gun tags with A)...

Here's the moment (the bug) where the logic switched off that node to a node it got stuck on...

My notes:
1. What should have happened is the resource A should have been picked up, but it looks like that node stopped returning true.
2. I would have also expected that once the bot was as close as to the resource as it could get (not pictured), that the logic would flow to the next node, then maybe switch right back, getting into a loop. This didn't happen, that move to closest resource node stayed lit (maybe a separate bug, maybe not a bug).
3. It also looks like the node to tag A, the closest resource in short range is returning true, but that action on that resource was completed many seconds earlier. Should that node light up like it's still happening?
Here's a snapshot before the bug, everything is working fine, the machine gun is trying to capture the A resource in short range (in this AI, only machine gun tags with A)...

Here's the moment (the bug) where the logic switched off that node to a node it got stuck on...

My notes:
1. What should have happened is the resource A should have been picked up, but it looks like that node stopped returning true.
2. I would have also expected that once the bot was as close as to the resource as it could get (not pictured), that the logic would flow to the next node, then maybe switch right back, getting into a loop. This didn't happen, that move to closest resource node stayed lit (maybe a separate bug, maybe not a bug).
3. It also looks like the node to tag A, the closest resource in short range is returning true, but that action on that resource was completed many seconds earlier. Should that node light up like it's still happening?