Error bloats up history database

Dear all,

I discovered that once there is an error in an async executed service task the task gets executed again and again and every error is included in the history table. This leads to > 1 Mio entries a day that consumes several GB and blocks the entire database in the end.

The point is that in the service task a class was named that was not existent. Therefore the error message

ENGINE-09008 Exception while instantiating class 'org.abc.common.CamundaServiceTasks.EmailTaskDelegate': ENGINE-09017 Cannot load class 'org.abc.common.CamundaServiceTasks.EmailTaskDelegate': org.abc.common.CamundaServiceTasks.EmailTaskDelegate  

Is repeated all over again in the table [ACT_HI_JOB_LOG]

Is there any chance to tell the engine not to repeat ad infinitum but to stop after xyz retries?

Thanks!