<?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 This is a scenario to be… in Product Forum</title>
    <link>https://community.blueprism.com/t5/Product-Forum/Exception-inside-recovery-mode/m-p/66242#M18847</link>
    <description>This is a scenario to be avoided at all costs, as any subsequent exception handling will probably not manage the new exception and there is every chance your process will fail. My advice is always to do a little as possible in recovery mode, and get past Resume as soon as you can. If you need to do anything beyond extracting the exception detail or updating the work&amp;nbsp;queue, then do it after the Resume. That way the original exception is neutralised and any coming after that are treated as 'new' exceptions. The mantra is to make sure you can only have 1 'live' exception at any one time.&amp;nbsp;</description>
    <pubDate>Thu, 11 Jan 2018 18:17:00 GMT</pubDate>
    <dc:creator>John__Carter</dc:creator>
    <dc:date>2018-01-11T18:17:00Z</dc:date>
    <item>
      <title>Exception inside recovery mode</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Exception-inside-recovery-mode/m-p/66241#M18846</link>
      <description>Hello,

What happens if another exception occurs while you are inside recovery mode (between Recover-Resume)? Can an outer page catch this exception and is it logical to design a block structure for this exception? If&amp;nbsp;a new exception is thrown does it replace the older one by overwriting exception detail and type?</description>
      <pubDate>Thu, 11 Jan 2018 16:22:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Exception-inside-recovery-mode/m-p/66241#M18846</guid>
      <dc:creator>OngunArisev</dc:creator>
      <dc:date>2018-01-11T16:22:00Z</dc:date>
    </item>
    <item>
      <title>This is a scenario to be…</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Exception-inside-recovery-mode/m-p/66242#M18847</link>
      <description>This is a scenario to be avoided at all costs, as any subsequent exception handling will probably not manage the new exception and there is every chance your process will fail. My advice is always to do a little as possible in recovery mode, and get past Resume as soon as you can. If you need to do anything beyond extracting the exception detail or updating the work&amp;nbsp;queue, then do it after the Resume. That way the original exception is neutralised and any coming after that are treated as 'new' exceptions. The mantra is to make sure you can only have 1 'live' exception at any one time.&amp;nbsp;</description>
      <pubDate>Thu, 11 Jan 2018 18:17:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Exception-inside-recovery-mode/m-p/66242#M18847</guid>
      <dc:creator>John__Carter</dc:creator>
      <dc:date>2018-01-11T18:17:00Z</dc:date>
    </item>
  </channel>
</rss>

