<?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 Apologies for the wrong… in Product Forum</title>
    <link>https://community.blueprism.com/t5/Product-Forum/scheduler/m-p/61222#M14559</link>
    <description>Apologies for the wrong information, currently you can't as the Scheduler will abort if your first process in the schedule fails. Alternatively, you can handle that at a process level, where you have an exception handling block to recover &amp;amp; catch some exceptions that can't be bubbled up (e.g&amp;nbsp;exceptions on the main page) to trigger the alternative process otherwise terminate the process (indirectly terminating the schedule).</description>
    <pubDate>Wed, 28 Feb 2018 01:42:00 GMT</pubDate>
    <dc:creator>Tolani.Jaiye-Tikolo</dc:creator>
    <dc:date>2018-02-28T01:42:00Z</dc:date>
    <item>
      <title>scheduler</title>
      <link>https://community.blueprism.com/t5/Product-Forum/scheduler/m-p/61219#M14556</link>
      <description>I want to run a second process immediately&amp;nbsp;from Scheduler when first terminates or aborts if an exception comes, is there any&amp;nbsp;way or solution to it?</description>
      <pubDate>Wed, 28 Feb 2018 01:03:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/scheduler/m-p/61219#M14556</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2018-02-28T01:03:00Z</dc:date>
    </item>
    <item>
      <title>Help on Scheduler</title>
      <link>https://community.blueprism.com/t5/Product-Forum/scheduler/m-p/61220#M14557</link>
      <description>Help on Scheduler</description>
      <pubDate>Wed, 28 Feb 2018 01:04:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/scheduler/m-p/61220#M14557</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2018-02-28T01:04:00Z</dc:date>
    </item>
    <item>
      <title>Hi MehulS,…</title>
      <link>https://community.blueprism.com/t5/Product-Forum/scheduler/m-p/61221#M14558</link>
      <description>Hi MehulS,
Yes, it's possible, you need to set the second process as the next task after the initial task in the Scheduler. Please, have a walk through the scheduler guide&amp;nbsp;http://portal.blueprism.com/system/files/2017-09/Blue%20Prism%20-%20Gui… provided by Blue Prism.
&amp;nbsp;</description>
      <pubDate>Wed, 28 Feb 2018 01:30:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/scheduler/m-p/61221#M14558</guid>
      <dc:creator>Tolani.Jaiye-Tikolo</dc:creator>
      <dc:date>2018-02-28T01:30:00Z</dc:date>
    </item>
    <item>
      <title>Apologies for the wrong…</title>
      <link>https://community.blueprism.com/t5/Product-Forum/scheduler/m-p/61222#M14559</link>
      <description>Apologies for the wrong information, currently you can't as the Scheduler will abort if your first process in the schedule fails. Alternatively, you can handle that at a process level, where you have an exception handling block to recover &amp;amp; catch some exceptions that can't be bubbled up (e.g&amp;nbsp;exceptions on the main page) to trigger the alternative process otherwise terminate the process (indirectly terminating the schedule).</description>
      <pubDate>Wed, 28 Feb 2018 01:42:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/scheduler/m-p/61222#M14559</guid>
      <dc:creator>Tolani.Jaiye-Tikolo</dc:creator>
      <dc:date>2018-02-28T01:42:00Z</dc:date>
    </item>
  </channel>
</rss>

