defaultNumberOfRetries not transparent

Camunda 7 Topics Discussion & Questions
1

Hi!

We have a Call Activity that calls a Service Task and that Service Task invokes a webservice.
The return-result is saved to the database and the process is finished.

Now we had an exception in the Service Task and the webservice was invoked 3 times.

The default of “defaultNumberOfRetries” is 3, but we set it to 1 in the bpm-platform.xml.

<properties>
  <property name="history">audit</property>
  <property name="databaseSchemaUpdate">true</property>
  <property name="authorizationEnabled">true</property>
  <property name="jobExecutorActivate">true</property>
  <property name="jobExecutorDeploymentAware">true</property>  
  <property name="defaultNumberOfRetries">1</property>
</properties>

I don’t understand why the job was executed 3 times. If the default takes place, mustn’t it be 4 attempts overall?
And why is the total job number not 2, because we set the NumberOfRetries to 1?

Can someone explain it?

Thanks!
Tim

2

Hi Tim,

Could you please share more regarding youw scenario - is it share or embedded, which camunda version do you use, which server do you use?
And is it possible to share the process with the failed service task?

Best regards,
Yana

3

In addition to what Yana wrote, the name defaultNumberOfRetries is a little bit misleading as this is actually the total number of execution attempts.

4