failedJobRetryTimeCycle for intermediateCatchEvent

[andreas1]

Since Activiti 5.16 the number of retries and the retry-wait-time can be configured like posted here:
https://app.camunda.com/confluence/display/foxUserGuide/Custom+Job+Retry+Strategy
(which was linked from http://jira.codehaus.org/browse/ACT-1046?focusedCommentId=351326&page=com.atlassian.jira.plugin.syst... )

I tried the same approach for an intermediateCatchEvent like this:

 <intermediateCatchEvent id="startProcessAsynch" name="StartProcessAsynch">
            <extensionElements>
                <activiti:failedJobRetryTimeCycle>R10/PT1M</activiti:failedJobRetryTimeCycle>
            </extensionElements>
            <timerEventDefinition>
                <timeDuration>${startProcessAsynchDelay}</timeDuration>
            </timerEventDefinition>    
</intermediateCatchEvent>
‍‍‍‍‍‍‍‍‍‍

It seems that this extensionElements has no effect and the default strategy (3 immediate retries) is applied.

How can I apply this configuration for an intermediateCatchEvent with Activiti >=5.16?

Thanks
Andreas

[trademak]

Hi Andreas,

That extension element is meant to be used for service tasks. What would the use case of adding this failedJobRetryTimeCycle to an intermediate catch event?

Best regards,

[andreas1]

Hi Tijs

For example, in my business-process I wait with an intermediate-catch-event a given amount of time. Afterwards the process continues with further gates and service-tasks. Each gate (they have complex logic with db-lookups, etc) and service-task (webservice-calls) can fail. So all this is executed in the job-context of the intermediate-catch-event. I would like to have also here a configurable retry-policy.
In general I think, everywhere where jobs are executed, there should be a configurable retry-policy. I like the approach with the extension-element, but it should be supported consistently "everywhere".

Regards
Andreas