We've uncovered another issue with the messaging between WM and LM, this time relating to travel from a sort location in receiving to a drop location. E.g. say there are several pallets sitting in sort locations on the receiving floor, and the putaway task path has a drop location between the receiving floor and the pallet's final location. In one of our buildings, one of the roles we have may end up taking a pallet from the sort location to the drop location, then returning to the receiving floor and picking up another pallet and taking that to a drop location, and so on. The first task of the day will have correct messaging - say he picks up a pallet from SORT-ACT21 and delivers it to DROP-ACT21. Those are the two locations that will come through on the message. But, then he'll return to the receiving floor, and maybe pick up a pallet from SORT-ACT83 and deliver it to DROP-ACT83. The message for this second task will have these 3 locations:
DROP-ACT21 (user's previous location)
DROP-ACT83 (here, it SHOULD be SORT-ACT83)
DROP-ACT83 (destination location)
So, the location in the second detail line of the message is incorrect, which causes errors in travel time. So far, I haven't been able to figure out why it works on the first task, but not for any subsequent task.