This will occur if you attempt to open an invalid Ticket ID. A text string containing spaces is not a valid id. It must be a single numeric value. In the case of your single ticket “16”, it should work. You would need to provide some more details of the state of things before those rules are fired.
Some actions are designed to work in specific contexts and don’t always behave as expected (until you become familiar with the valid contexts and limits). The Ticket screen is a special case for example. It’s a “modal” screen which means it needs to be closed before various other actions are recognized. It’s living in a kind of protected environment, it can only work on one ticket at a time, so that places restrictions on what you do while a ticket is open.
You need to be aware of the execution context of rules (events) and become familiar with the available TAG values in each event. Be careful about assuming which data is available in each rule.
While building new automation it is very useful to display a lot of debugging values using Show Message in every rule.
These are generic suggestions and maybe not directly related to this specific issue.