question

The simplest solution here, as you said, is to check the Ignore Inactive Members box. If your desire is to get the active members to travel around the inactive members, I guess I disagree with your desire. That generally would not be a desired solution. When a truck is idle, other trucks should not move around him. He should get out of the way. So you should have some logic, likely through process flow, to tell a transporter to go somewhere when he's not doing anything, so that he doesn't get in other people's way when he's not doing anything. This is the solution that would be true to real life. As for trucks that are actively loading/unloading, I would think you'd probably have a passing lane in the center of the aisle, and trucks mainly stay in the passing lane, then veer off the center lane to load/unload. You can do this by having a preferred path in the center of the aisle. Trucks will get on that preferred path when they're traveling, and get off it when they're loading/unloading.

If neither of these solutions work for you, then you can also have a process flow that listens to the Transporter's OnAStarBlock event, and then reroute the guy around the blockage as you desire. When we implemented collision avoidance, we decided that any canned "get out of the way" mechanism for simple blockages would likely only work in a small percentage of scenarios, because different scenarios would likely have different means for avoiding blockage. So we just provided the OnAStarBlock and OnAStarContinue events, and just let you roll your own.

There is functionality under the hood where you can create temporary barriers before performing routing. Perhaps we may expose this functionality to FlexScript so that the user can create temporary barriers before dispatching the transporter. However, I don't foresee us implementing much canned functionality any time soon. There are just too many scenarios where canned functionality falls apart.