Execute Print Job Action - Print Ticket parameter

No it’s not recent. I’ve been having problem for quite a while, in V4 as well. I posted about it before and you said it was because I had modified something:

I thought it was related to cancelled tickets but actually just starting a new ticket then closing without doing anything also caused it.

I finally broke down the setup and compared bit by bit against the sample database and found out that it is the writing to customer display that was causing it, and specifically by setting Print Ticket to False was stopping it with this annoying behaviour.

Incrementing ticket number (note: not ticket id) is somewhat annoying - it doesn’t cause any real issue, however I started getting clients ask where is ticket #103 because they see #102 and #104 via the UI. Accountants also query such missing things and think its some fraud going on.