nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

How to detect / manually re-run tasks that have failed after retries

jesper1

If you have an asynchronous task which is a JavaDelegate task, and it throws an exception, then Activiti can automatically retry it a number of times according to a schedule, as is described in section 8.7.2 of the user manual.

What happens to a process instance when the retry counter reaches zero? Does it just stay waiting at the failed task forever?

Is it possible to query for processes which have gotten into such a state, and is it possible to manually retry such a task (e.g. through an API call)?

Find more posts tagged with

Comments

martin_grofcik

Hi Jasper.

What happens to a process instance when the retry counter reaches zero?

retries is set to 0. You can fetch jobs with no retries left.

is it possible to manually retry such a task (e.g. through an API call)?

yes, e.g.

<br>&nbsp; /** <br>&nbsp;&nbsp; * Forced synchronous execution of a job (eg. for administation or testing)<br>&nbsp;&nbsp; * The job will be executed, even if the process definition and/or the process instance<br>&nbsp;&nbsp; * is in suspended state.<br>&nbsp;&nbsp; * <br>&nbsp;&nbsp; * @param jobId id of the job to execute, cannot be null.<br>&nbsp;&nbsp; * @throws ActivitiObjectNotFoundException when there is no job with the given id. <br>&nbsp;&nbsp; */<br>&nbsp; void executeJob(String jobId);<br>

Regards
Martin

jesper1

Hello Martin,

Thanks for your reply. I've discovered that I can indeed query for jobs that have no retries left and that failed with an exception, using the ManagementService:

<br>List<Job> failedJobs = managementService.createJobQuery()<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; .withException().noRetriesLeft()<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; .orderByJobDuedate().desc().list();<br>

And then re-run those jobs with executeJob(). As the documentation says, this will run the job synchronously, in the thread that calls the executeJob() method.

I've seen there's also a way to set the number of retries on a job, but if I do that then Activiti is not automatically going to pick up and run the job using the job executor that I've configured the engine with.