Hi Braam Koekekemoer,
It can happen than orphan records remain in APLLCK table. Normally, once is user is logged out or batch task finished, all records from APLLCK should have been deleted. There is no embedded task to clear it, but you can:

• Create a recurring batch task running daily that deletes the records or produces a "Truncate Table" with ExecSQL"
• Create a SQL job that does a truncate table

Obviously, do this during non-business hours and make sure there are no users connected, no web services or batch task running.

Here's a document that explores the deletion of dead lock records in a bit more detail:

https://drive.google.com/file/d/1Z4gI0NFpuW7wuMiuitAEGH1vqKon41LZ/view?usp=sharing

Essentially, it allows you to delete just the records that no longer have a valid user session associated with them and should be a bit safer than truncating the table.