I have noticed in v5.2.23 beta, and also in v5.2.22 that the Terminal in Print Job mappings appear to be ignored.
I have tested like this:
2 terminals each are sending to a different network printer to open the cash drawer.
When I test this scenario, no matter what terminal the print job is executed from, POS1 cash drawer is opening. If I delete the POS1 mapping and only leave POS2 mapping, then as expected POS2 cash drawer will open.
So it would seem Terminal is being ignored / not handled properly in the mapping.
I had a similar issue recently that was on v5.2.22 where I had a print job with a few different cases of printing different places depending on Terminal, Ticket Type and Product Tag. I was certain the mappings were all setup properly but it was printing what appeared to be randomly from different terminals, or not printing at all from some. I couldn’t get to the bottom of it and then just spread out the setup to multiple print jobs and multiple execute actions, therefore complicating the setup but also simplifying the print job mappings, and it worked then.
I don’t have a copy of the more complex mappings to hand but the above case can be reproduced and is more simple, and I believe is where the root cause lies.