History and reprinting

Verlauf is the record of every job: which file, from which folder, to which printer, when, and how it ended.

Reading a row

Each entry shows the file name, the folder it came from, the printer it went to, the time it finished, and its outcome. A failed job also shows why it failed.

A job outlives the folder it came from. Delete a folder and its history stays, showing Gelöschter Ordner in place of the name — the record of what was printed does not disappear because the rule that produced it did.

Nur Fehler

The switch filters the list down to failures.

It is a real query, not a filter over what is on screen: with the filter on you get the most recent failures, not the failures among the most recent jobs. A failure from last week still shows up even if a thousand successful jobs have run since.

Erneut drucken

Every finished or failed job can be printed again.

A reprint creates a new job rather than reviving the old one, so the history keeps both entries — you can always see that something was printed twice and when.

The new job uses the settings recorded on the original job, not whatever the folder is set to now. Reprinting a job from three weeks ago sends it to the printer it was meant for, with the copy count it was meant to have.

When a reprint is refused

The file has to still be there. If it was moved, archived or deleted since, Printy says so instead of failing silently.

With the default post-print rule this is the normal case for older jobs: the file is in printed or failed, not where it was. Move it back into the watched folder and it will be picked up as a new file — which is usually simpler than reprinting.

Jobs that have not finished yet — Wartet, Druckt, Wiederholt — offer no reprint button. They are already on their way; adding a second copy of the same file to the queue would just print it twice.

How far back it goes

The screen loads the most recent 300 entries. Older jobs stay in the database and are counted, but are not listed.