Keep finished jobs in the database for history, but skip it while processing the queue

[sadpenguinn]

It's a useful feature to keep finished jobs in the database. Especially for production environment where this feature can help to discover bug cases in service logic by keeping failed and successful jobs. Clients can use it as well as logs.
Gue will ensure to keep finished jobs in the database using the job's 'SkipDelete' property. But client should handle and monitor the memory size that these jobs take up and reduce the size when it's necessary.

[vgarvardt]

Hooks were designed specifically for this purpose - you can set one with WithWorkerHooksJobDone or WithPoolHooksJobDone and store finished jobs to the log with all the additional required information. This will fulfill your requirement and keep the table and code untouched.