<?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 Re: Timer based Processes and Exceptions in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/timer-based-processes-and-exceptions/m-p/128307#M90211</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;The job-executor can contain jobs that aren't related to any process-instance, but rather only to a proc-def. So it's normal for a timer-cycle start-event to have only a single job entry.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;As we leverage "jobs" for the timer-start event and only a single job exists per process-definition (with a timer-start-event), the job won't run again if the job failed 3 times. So if the retry-count is set to 0, it won't be retried even if the next time-cycle has arrived. This is just the way this is implemented right now…&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 01 Feb 2013 16:21:17 GMT</pubDate>
    <dc:creator>frederikherema1</dc:creator>
    <dc:date>2013-02-01T16:21:17Z</dc:date>
    <item>
      <title>Timer based Processes and Exceptions</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/timer-based-processes-and-exceptions/m-p/128306#M90210</link>
      <description>Hi,I noticed that a process, that has a timer start event (time cycle, cron: */15 * * * * ?) and starts automatically after deploy won't be executed anymore if an exception was thrown within that process.Only anew deployment will start that cycle again. Does anyone knows that problem?Furthermore it</description>
      <pubDate>Fri, 01 Feb 2013 15:52:49 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/timer-based-processes-and-exceptions/m-p/128306#M90210</guid>
      <dc:creator>bzeuner</dc:creator>
      <dc:date>2013-02-01T15:52:49Z</dc:date>
    </item>
    <item>
      <title>Re: Timer based Processes and Exceptions</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/timer-based-processes-and-exceptions/m-p/128307#M90211</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;The job-executor can contain jobs that aren't related to any process-instance, but rather only to a proc-def. So it's normal for a timer-cycle start-event to have only a single job entry.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;As we leverage "jobs" for the timer-start event and only a single job exists per process-definition (with a timer-start-event), the job won't run again if the job failed 3 times. So if the retry-count is set to 0, it won't be retried even if the next time-cycle has arrived. This is just the way this is implemented right now…&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Feb 2013 16:21:17 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/timer-based-processes-and-exceptions/m-p/128307#M90211</guid>
      <dc:creator>frederikherema1</dc:creator>
      <dc:date>2013-02-01T16:21:17Z</dc:date>
    </item>
  </channel>
</rss>

