When the restaurant is busy the chef looses track of orders as the ticket layout jumps around when you add a cold drink to the tables bill.
So the food ticket has been waiting for 15 mins and is in front of the que, the waiter then adds a cold drink to the bill and then the table’s minutes waiting changes with the addition of a cold drink on the kitchen display back to 1 min. The chef then thinks it is an new order.
This way is obviously a recipe for disaster, is there a way to not have cold drinks update the tables waiting time.
Ticket’s Status state updates every time you add an order. You can maintain a separate state that updates only when food orders added. You can use this state instead of using Status state in {TICKET STATE MINUTES:Status} tag.
Create a new action that updates Ticket’s KitchenStatus state.
Execute it every time you add a new food order.
Use {TICKET STATE MINUTES:KitchenStatus} to display time.
Emre is suggesting you create and use a differentState other than Status, such as KitchenStatus or similar. This is to separate Food and Drink Ticket States.
So your Rule looks fine, but the Action you are using updates the Status State. You should have it update something like KitchenStatus State instead, then use {TICKET STATE MINUTES:KitchenStatus} in your Template.