Hi,

I would like to suggest a possible optional improvement related to failed print jobs when using PrintNode.

We currently have a pizzeria / restaurant client using Printus successfully in production. Overall, the system works very well, but we have observed a single failed print out of ~20 successful prints, caused by a temporary “printer busy” state reported by PrintNode.

In real-world environments (restaurants, kitchens, ticket printers), these kinds of transient issues can happen occasionally (printer busy, USB hiccup, brief offline state, PrintNode delay). When this occurs, the order is not printed and requires manual intervention.

Proposed idea (optional and non-intrusive):

Add an optional automatic retry mechanism when a PrintNode print job fails.

Configurable retry attempts (for example: 1 to 3 retries maximum).

Configurable retry interval (for example via WP-Cron every 3–5 minutes).

Disabled by default, to preserve the current lightweight and minimal behavior.

This could be implemented as a background check that only monitors failed print jobs, without reprocessing successful ones.

Additionally, it would be very helpful if:

The Reprint button on the order page always keeps the last used printer and template preselected, so manual recovery is faster when needed. I understand this may already be under consideration for future updates.

This feature would not be intended to change the normal workflow, but rather to make the system more robust against rare, temporary printer states, especially in unattended environments such as kitchens.

Thanks for considering this suggestion, and congratulations on the excellent work with Printus.

Best regards.
Angel