Details
-
Bug Report
-
Resolution: Unresolved
-
L3 - Default
-
None
-
7.9.0
-
None
-
None
-
Linux Debian 7.11
Camunda Tomcat Bundle 7.9.0
Java 8
Description
Reference in the forum: https://forum.camunda.org/t/job-executor-getretries-is-wrong-in-some-cases/9470/5
The first time a task is executed under a job, it is getting a false number of retries left. That's misleading. Example with a script Task in groovy:
jobExecutorContext = Context.getJobExecutorContext();
println jobExecutorContext.getCurrentJob().getRetries();
throw new Exception("...");
And in the task fields I set Retry Time Cycle to be: "R10/PT10"
Expected: In the log, the first time I get a number that shoud be consistent with the retry cycle I set for the asychronous task
10
... (Exception)
9
... (Exception)
8 ... and so on until 1.
What currently happens: the first number is always '3'.
3
... (Exception)
9
... (Exception)
8 ... and so on until 1