AnsweredAssumed Answered

Handling different retry parameters

Question asked by spartan on May 19, 2016
Latest reply on May 31, 2016 by jbarrez

I have to implement my process taking into account that some services can be retried (example : timeout while calling web services). The maximum number of retries and the delay can be different from a service to another one.

One designer suggested that we design this using the modeler and adding trivial branching/looping/exit. I disagreed because that was just going to make the diagram less readable because of non-business concern. Also Activiti is supposed to provide a retry mechanism, let's just re-use and not re-do.

1) Whats do you think about that ? Better to design it on the diagram or rather handle/hide on in the java side ?

2) How to actually use the retry mechanism provided by Activiti ? By default, there are 3 retries hardcoded. How to make a diffrent number of retries for each of my services ?