problem

If a user just closes its editor window, translate5 does not notice this, and therefore the task and the corresponding user job is still locked.

To solve this the application sends a logout request to the server when the window is closed, but this does not work always probably prevented by the browser.

This is mostly annoying when translate5 is embedded and directly after leaving / closing the translate5 editor the task should be processed by the leading system via API.

solution

In that case translate5 should check on accessing the job if the locking session still has a connection in the messagebux, if not the job and task should be unlocked.

Further improvement: The garbage collector should also check the locked tasks if the locking user has no connection. If not then the task should unlocked. This reduces the unwanted locking time to at least 15 minutes (the default/recommended configuration of the periodical cron job). ATTENTION DANGEROUS - just unlocking tasks if a session has no connection is no solution since task locking is also made by workers which are per definition without a connection. Solution: must be implemented by using the valid session session SQL or sessions with connection in the tua clean up. Collect there the affected jobs and use the tasks unlockForUser on them.