<?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 There is a fix in the latest in Product Forum</title>
    <link>https://community.blueprism.com/t5/Product-Forum/Not-able-to-stop-the-session-and-status-shows-Stopping-in/m-p/60601#M14035</link>
    <description>There is a fix in the latest version of Blue Prism for this issue:
When a Runtime Resource is re-started following a hard shutdown, any processes that were in a stopping state will now be appropriately marked as terminated.
bg-165 9833</description>
    <pubDate>Tue, 30 May 2017 14:11:00 GMT</pubDate>
    <dc:creator>Denis__Dennehy</dc:creator>
    <dc:date>2017-05-30T14:11:00Z</dc:date>
    <item>
      <title>Not able to stop the session and status shows Stopping in Control room of Interactive Client.</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Not-able-to-stop-the-session-and-status-shows-Stopping-in/m-p/60600#M14034</link>
      <description>Not able to stop the session and status shows Stopping in Control room of Interactive Client.

Tried the following still no solution and appreciate help on this.
1) Immediate stop on session in control room. Status shows "Stopping" and not "Terminated".
2) Tried requeststop command in runtime resource machine.
2) Restarted runtime resource port.</description>
      <pubDate>Sat, 27 May 2017 00:59:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Not-able-to-stop-the-session-and-status-shows-Stopping-in/m-p/60600#M14034</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2017-05-27T00:59:00Z</dc:date>
    </item>
    <item>
      <title>There is a fix in the latest</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Not-able-to-stop-the-session-and-status-shows-Stopping-in/m-p/60601#M14035</link>
      <description>There is a fix in the latest version of Blue Prism for this issue:
When a Runtime Resource is re-started following a hard shutdown, any processes that were in a stopping state will now be appropriately marked as terminated.
bg-165 9833</description>
      <pubDate>Tue, 30 May 2017 14:11:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Not-able-to-stop-the-session-and-status-shows-Stopping-in/m-p/60601#M14035</guid>
      <dc:creator>Denis__Dennehy</dc:creator>
      <dc:date>2017-05-30T14:11:00Z</dc:date>
    </item>
    <item>
      <title>Hi Denis,
We restarted the…</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Not-able-to-stop-the-session-and-status-shows-Stopping-in/m-p/60602#M14036</link>
      <description>Hi Denis,
We restarted the machine but still the process shows as Stopping is it something to do with the BP version that we are using&amp;nbsp;
our BP version is 5.0.23
So for this version is there any work around to make these process has terminated..</description>
      <pubDate>Fri, 31 Aug 2018 12:29:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Not-able-to-stop-the-session-and-status-shows-Stopping-in/m-p/60602#M14036</guid>
      <dc:creator>ManojKumar3</dc:creator>
      <dc:date>2018-08-31T12:29:00Z</dc:date>
    </item>
  </channel>
</rss>

