Beta #738 is now building that should address 1/2 of the problem. (#737 contained debugging code that breaks the bot by accident!)
The Poi code that was rewritten would move the bot into range of portals to ensure it could find the portal and then interact with it. On my resolution, I didn't have interaction issues unless I purposefully moved the character to a place I knew was going to have an issue. However, for smaller resolutions, the portal would just be out of range. When I was retesting earlier in the thread, my portals were spawning in a position that wouldn't cause problems, but after playing with getting them to spawn in more random locations (take area transition into town rather than the portal) I could see the potential issue.
Now, the bot will move towards the portal area, and then move to the portal itself before interacting.
However, that leads to the second 1/2 of the problem you are having. I didn't even realize it was happening until I was looking at your screenshot and noticed you don't have gui labels on.
As it turns out, our code seems to break in several places when they are disabled. I retested normally like I did before with them off, and the bot simply wouldn't take the portal at all. Upon enabling the debugging cursor, I saw why. For now, please hit the Z key or enable the "Always Highlight" in game so the bot can find the entity to interact with correctly. We need to rewrite some of the core code to address this issue, I thought it used to work properly, but now it seems it doesn't anymore.
I always play/test with those gui labels on, so that's why I never had a lot of the issues other users have been reporting, but now I know.