<?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: Re-run incomplete workflows on server startups in Alfresco Forum</title>
    <link>https://connect.hyland.com/t5/alfresco-forum/re-run-incomplete-workflows-on-server-startups/m-p/6969#M3353</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&amp;nbsp;&lt;B&gt;Jogin Mehta&lt;/B&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;BLOCKQUOTE class="jive_macro_quote jive-quote jive_text_macro"&gt;&lt;P style="border: 0px;"&gt;1. I have workflow with N number of sync job nodes.&lt;/P&gt;&lt;P style="border: 0px;"&gt;2. Let's say after performing some jobs server goes down.&lt;/P&gt;&lt;P style="border: 0px;"&gt;3. Whenever server is restarted, activiti should start the workflows automatically.&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;SPAN style="color: #727174; background-color: #ffffff; border: 0px;"&gt;The answer is yes. Process execution should be restarted when the server is back.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #727174; background-color: #ffffff; border: 0px;"&gt;By default, Activiti configures a job to be retried up to 3 times upon failure. If your jobs had reached 3 times of retry because of the server down situation, you can manually restart the jobs by activiti-explorer or using the Activiti API such as Activiti REST calls.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have you experimented this? Have you tried this in your environment?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Thong Huynh&lt;/P&gt;&lt;P&gt;&lt;A href="https://migration33.stage.lithium.com/t5/tag/bp3/tg-p"&gt;&lt;/A&gt;‌&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 16 Feb 2017 02:43:30 GMT</pubDate>
    <dc:creator>thuynh</dc:creator>
    <dc:date>2017-02-16T02:43:30Z</dc:date>
    <item>
      <title>Re-run incomplete workflows on server startups</title>
      <link>https://connect.hyland.com/t5/alfresco-forum/re-run-incomplete-workflows-on-server-startups/m-p/6968#M3352</link>
      <description>Hi All,I would like to know, whether activiti has some built-in functionality for below scenario:1. I have workflow with N number of sync job nodes.2. Let's say after performing some jobs server goes down.3. Whenever server is restarted, activiti should start the workflows automatically.Thanks,Jogin</description>
      <pubDate>Tue, 14 Feb 2017 07:21:19 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-forum/re-run-incomplete-workflows-on-server-startups/m-p/6968#M3352</guid>
      <dc:creator>jogin</dc:creator>
      <dc:date>2017-02-14T07:21:19Z</dc:date>
    </item>
    <item>
      <title>Re: Re-run incomplete workflows on server startups</title>
      <link>https://connect.hyland.com/t5/alfresco-forum/re-run-incomplete-workflows-on-server-startups/m-p/6969#M3353</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&amp;nbsp;&lt;B&gt;Jogin Mehta&lt;/B&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;BLOCKQUOTE class="jive_macro_quote jive-quote jive_text_macro"&gt;&lt;P style="border: 0px;"&gt;1. I have workflow with N number of sync job nodes.&lt;/P&gt;&lt;P style="border: 0px;"&gt;2. Let's say after performing some jobs server goes down.&lt;/P&gt;&lt;P style="border: 0px;"&gt;3. Whenever server is restarted, activiti should start the workflows automatically.&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;SPAN style="color: #727174; background-color: #ffffff; border: 0px;"&gt;The answer is yes. Process execution should be restarted when the server is back.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #727174; background-color: #ffffff; border: 0px;"&gt;By default, Activiti configures a job to be retried up to 3 times upon failure. If your jobs had reached 3 times of retry because of the server down situation, you can manually restart the jobs by activiti-explorer or using the Activiti API such as Activiti REST calls.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have you experimented this? Have you tried this in your environment?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Thong Huynh&lt;/P&gt;&lt;P&gt;&lt;A href="https://migration33.stage.lithium.com/t5/tag/bp3/tg-p"&gt;&lt;/A&gt;‌&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 16 Feb 2017 02:43:30 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-forum/re-run-incomplete-workflows-on-server-startups/m-p/6969#M3353</guid>
      <dc:creator>thuynh</dc:creator>
      <dc:date>2017-02-16T02:43:30Z</dc:date>
    </item>
    <item>
      <title>Re: Re-run incomplete workflows on server startups</title>
      <link>https://connect.hyland.com/t5/alfresco-forum/re-run-incomplete-workflows-on-server-startups/m-p/6970#M3354</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi &lt;A __default_attr="164357" __jive_macro_name="user" _jive_internal="true" data-id="164357" data-objecttype="3" data-type="person" href="https://community.alfresco.com/people/thuynh" rel="nofollow noopener noreferrer"&gt;&lt;/A&gt;‌&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your reply.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have seen retry mechanism for asynchronous jobs, where in workflow we specify activiti:async=true. For synchronous jobs it doesn't persist anything in database until whole workflow gets completed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So, for synchronous jobs there seems to be no direct way to re-run workflow on startup.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Jogin&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 16 Feb 2017 09:34:57 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-forum/re-run-incomplete-workflows-on-server-startups/m-p/6970#M3354</guid>
      <dc:creator>jogin</dc:creator>
      <dc:date>2017-02-16T09:34:57Z</dc:date>
    </item>
  </channel>
</rss>

