<?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 We are facing similar issue;… in Product Forum</title>
    <link>https://community.blueprism.com/t5/Product-Forum/Checking-if-robot-is-freezing/m-p/52619#M7465</link>
    <description>We are facing similar issue; the bot completely freezes when working with a browser based application but in control room it appears to be running. Can you please elaborate on the solution for this issue as it seams&amp;nbsp;that the bot just doesn't move forward or&amp;nbsp;go to&amp;nbsp;the timeout exception route as well.</description>
    <pubDate>Fri, 19 Jan 2018 06:26:00 GMT</pubDate>
    <dc:creator>SagarMehta</dc:creator>
    <dc:date>2018-01-19T06:26:00Z</dc:date>
    <item>
      <title>Checking if robot is freezing</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Checking-if-robot-is-freezing/m-p/52617#M7463</link>
      <description>Hi,
it sometimes happens that a robot freezes when executing a task. However, in the control room it appears to be running. Is there a way i.e. to be able to notice a certain item in a queue has been locked for too long or a robot has not executed the next step in a process for too long? I am not looking for a solution to fix the freezing in this particular situation, I just wonder if there is a general approach that could be used to determine if a robot is really proceeding or hanging.</description>
      <pubDate>Mon, 06 Jun 2016 20:15:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Checking-if-robot-is-freezing/m-p/52617#M7463</guid>
      <dc:creator>ArchiveUser</dc:creator>
      <dc:date>2016-06-06T20:15:00Z</dc:date>
    </item>
    <item>
      <title>You should build in pre</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Checking-if-robot-is-freezing/m-p/52618#M7464</link>
      <description>You should build in pre-condition and post-condition checks to each action to see if the virtual worker has performed the task it was asked to. You should build in a loop around these checks with a relevant wait stage between each check and after reaching a loop limit, throw an exception to kill the process. This will them terminate the session. If you are using a queue and are logging your work steps or items cleverly then you should be able to re-initiate the process and it should pick back up where it left off.</description>
      <pubDate>Tue, 07 Jun 2016 18:11:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Checking-if-robot-is-freezing/m-p/52618#M7464</guid>
      <dc:creator>TomBlackburn1</dc:creator>
      <dc:date>2016-06-07T18:11:00Z</dc:date>
    </item>
    <item>
      <title>We are facing similar issue;…</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Checking-if-robot-is-freezing/m-p/52619#M7465</link>
      <description>We are facing similar issue; the bot completely freezes when working with a browser based application but in control room it appears to be running. Can you please elaborate on the solution for this issue as it seams&amp;nbsp;that the bot just doesn't move forward or&amp;nbsp;go to&amp;nbsp;the timeout exception route as well.</description>
      <pubDate>Fri, 19 Jan 2018 06:26:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Checking-if-robot-is-freezing/m-p/52619#M7465</guid>
      <dc:creator>SagarMehta</dc:creator>
      <dc:date>2018-01-19T06:26:00Z</dc:date>
    </item>
    <item>
      <title>Freezing as you describe…</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Checking-if-robot-is-freezing/m-p/52620#M7466</link>
      <description>Freezing as you describe sounds very unusual. Although a 'global timeout' feature was introduced into BP recently, I would side with Tom's advice to look again&amp;nbsp;at the object logic, maybe the process exception handling too. Check that the process has not fallen into a nasty&amp;nbsp;infinite loop, and also check that the problem isn't dues to the classic 'it works in process studio but fails in control room' - that is almost always down to weak logic around Wait stages.</description>
      <pubDate>Fri, 19 Jan 2018 14:24:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Checking-if-robot-is-freezing/m-p/52620#M7466</guid>
      <dc:creator>John__Carter</dc:creator>
      <dc:date>2018-01-19T14:24:00Z</dc:date>
    </item>
    <item>
      <title>If you cannot get the latest…</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Checking-if-robot-is-freezing/m-p/52621#M7467</link>
      <description>If you cannot get the latest version of Blue Prism with the global timeout feature John mentions - I recommend investigating where your application is hanging.&amp;nbsp; More often then not it will always be occuring in the same place.&amp;nbsp; The cause will be that Blue Prism calls an interface function (such as click button) and does not get a response from that function.&amp;nbsp; An unexpected pop up can sometimes prevent the expected response.&amp;nbsp; &amp;nbsp;If you figure out a consistent place where the issue is happening try replacing interface Clicks/Presses with a global click to see if it stops the problem (with a global click Blue Prism is not waiting for a function response).</description>
      <pubDate>Fri, 19 Jan 2018 16:37:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Checking-if-robot-is-freezing/m-p/52621#M7467</guid>
      <dc:creator>Denis__Dennehy</dc:creator>
      <dc:date>2018-01-19T16:37:00Z</dc:date>
    </item>
  </channel>
</rss>

