Delete Job - why would you do that?

[jritter]

Hi

I'm trying to understand asynchronous executions, and was experimenting with error handling. As far as I've understood, the default behaviour if an exception is thrown in an async service task is to retry 3 times. Activiti Explorer offers an option to execute this job, which does a retry.

What I've also noticed is that the API as well as the activiti explorer offers a "Delete Job" functionality, which I've a hard time to understand. Isn't it true that for each deleted job there is an orphaned process instance left behind? As far as I can tell - also from posts in this forum - there is no way to rehydrate this job. So what is the intention behind this operation?

Thanks and regards,
Jürg

[trademak]

Hi Jürg,

Deleting a job is a very uncommon use case for a job created by a process instance indeed. But the job mechanism in Activiti is open for use of your own custom job types as well. And for custom job types it could be useful to be able to delete them.

Best regards,

[jritter]

Hi Tijs

Thanks a lot for your comment, I really appreciate it. That makes sense.

Best regards,
Jürg