Retrying a service task

Camunda 7 Topics Discussion & Questions
1

Dear fellow Camunda users,

I’m in need a of little advice. I’m interested in retrying service tasks when they don’t complete. I’m wondering what ways are possible and are best to resolve this issue?

Consider these two scenarios.

Scenario A:
My service task is supposed to collect some data about an account but is unable to do so. I’d like Camunda to instruct the tasks to try again after 5 seconds, once more after an hour and a last time after 24 hours. Should it fail then I’d like it to terminate the process.

Scenario B:
My service task is supposed to make a mutation in system A. The service task fails and when it does I’d like it to wait 5 seconds and then go back two tasks in my process and follow the normal execution. When it arrives and it still can’t complete I’d like it to go back two after 10 minutes and follow normal execution. The third time I’d like it to terminate the whole process.

Anyone have some advice how to tackle these scenarios and/or some general advice about how to handle retrying in Camunda? Many thanks in advance for any help.

kind regards,

T

2

Just to clarify; I’m not looking for a modeled solution to loop the task but a configurable solution on the task itself. If that’s not an achievable method maybe a timer would be acceptable as well but preferably a solution in the property panel of the task. Thanks again for anyone who can offer help.

T

3

Any takers :)?

4

I am also interested in a solution for this. Please advise

5

Hi @kingspallett,

for Scenario A have a look at the docs.: https://docs.camunda.org/manual/7.10/user-guide/process-engine/the-job-executor/#retry-intervals (And maybe the stuff around this paragraph…)

Hope this helps, Ingo

2 Likes
6

Hi @Ingo_Richtsmeier,

Thanks for your reply, I’m going to check it out and post an update here.

kind regards,

T

7

Hi,

Scenario A is quite ‘easy’ as it seems; as of yet I have not found a good solution (with good I mean a clean modeled solution) to model scenario B where my process has to jump back a couple of tasks. Any advice?