<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic failedJobRetryTimeCycle for intermediateCatchEvent in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/failedjobretrytimecycle-for-intermediatecatchevent/m-p/179218#M132348</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Since Activiti 5.16 the number of retries and the retry-wait-time can be configured like posted here:&lt;/SPAN&gt;&lt;BR /&gt;&lt;A href="https://app.camunda.com/confluence/display/foxUserGuide/Custom+Job+Retry+Strategy" rel="nofollow noopener noreferrer"&gt;https://app.camunda.com/confluence/display/foxUserGuide/Custom+Job+Retry+Strategy&lt;/A&gt;&lt;BR /&gt;&lt;SPAN&gt;(which was linked from &lt;/SPAN&gt;&lt;A href="http://jira.codehaus.org/browse/ACT-1046?focusedCommentId=351326&amp;amp;page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-351326" rel="nofollow noopener noreferrer"&gt;http://jira.codehaus.org/browse/ACT-1046?focusedCommentId=351326&amp;amp;page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-351326&lt;/A&gt;&lt;SPAN&gt; )&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I tried the same approach for an intermediateCatchEvent like this:&lt;/SPAN&gt;&lt;BR /&gt;&lt;PRE class="language-none line-numbers"&gt;&lt;CODE&gt;&lt;BR /&gt; &amp;lt;intermediateCatchEvent id="startProcessAsynch" name="StartProcessAsynch"&amp;gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;extensionElements&amp;gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;activiti:failedJobRetryTimeCycle&amp;gt;R10/PT1M&amp;lt;/activiti:failedJobRetryTimeCycle&amp;gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;/extensionElements&amp;gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;timerEventDefinition&amp;gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;timeDuration&amp;gt;${startProcessAsynchDelay}&amp;lt;/timeDuration&amp;gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;/timerEventDefinition&amp;gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;BR /&gt;&amp;lt;/intermediateCatchEvent&amp;gt;&lt;BR /&gt;&lt;SPAN class="line-numbers-rows"&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;SPAN&gt;‍&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;It seems that this extensionElements has no effect and the default strategy (3 immediate retries) is applied.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;How can I apply this configuration for an intermediateCatchEvent with Activiti &amp;gt;=5.16?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Andreas&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 22 Sep 2014 12:34:17 GMT</pubDate>
    <dc:creator>andreas1</dc:creator>
    <dc:date>2014-09-22T12:34:17Z</dc:date>
    <item>
      <title>failedJobRetryTimeCycle for intermediateCatchEvent</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/failedjobretrytimecycle-for-intermediatecatchevent/m-p/179218#M132348</link>
      <description>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&amp;amp;page=com.atlassian.jira.pl</description>
      <pubDate>Mon, 22 Sep 2014 12:34:17 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/failedjobretrytimecycle-for-intermediatecatchevent/m-p/179218#M132348</guid>
      <dc:creator>andreas1</dc:creator>
      <dc:date>2014-09-22T12:34:17Z</dc:date>
    </item>
    <item>
      <title>Re: failedJobRetryTimeCycle for intermediateCatchEvent</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/failedjobretrytimecycle-for-intermediatecatchevent/m-p/179219#M132349</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi Andreas,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;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?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Best regards,&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 24 Sep 2014 04:45:50 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/failedjobretrytimecycle-for-intermediatecatchevent/m-p/179219#M132349</guid>
      <dc:creator>trademak</dc:creator>
      <dc:date>2014-09-24T04:45:50Z</dc:date>
    </item>
    <item>
      <title>Re: failedJobRetryTimeCycle for intermediateCatchEvent</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/failedjobretrytimecycle-for-intermediatecatchevent/m-p/179220#M132350</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi Tijs&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;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.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;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".&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Andreas &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 24 Sep 2014 06:21:07 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/failedjobretrytimecycle-for-intermediatecatchevent/m-p/179220#M132350</guid>
      <dc:creator>andreas1</dc:creator>
      <dc:date>2014-09-24T06:21:07Z</dc:date>
    </item>
  </channel>
</rss>

