<?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 Force re-tried items in Product Forum</title>
    <link>https://community.blueprism.com/t5/Product-Forum/Force-re-tried-items/m-p/78230#M30279</link>
    <description>Apologies if this has been asked before, but when a queue items is re-tried using the "force re-try" option in the queue, is there any way to tell which user initiated this action?
We've seen a couple of isolated incidents where it seems controllers have decided to retry items at a later date, which has had some undesired consequences - it's not catastrophic, but none-the-less I'd like to re-educate the controller if I can identify the individual(s) concerned.</description>
    <pubDate>Mon, 04 Jun 2018 20:10:00 GMT</pubDate>
    <dc:creator>NeilPannett</dc:creator>
    <dc:date>2018-06-04T20:10:00Z</dc:date>
    <item>
      <title>Force re-tried items</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Force-re-tried-items/m-p/78230#M30279</link>
      <description>Apologies if this has been asked before, but when a queue items is re-tried using the "force re-try" option in the queue, is there any way to tell which user initiated this action?
We've seen a couple of isolated incidents where it seems controllers have decided to retry items at a later date, which has had some undesired consequences - it's not catastrophic, but none-the-less I'd like to re-educate the controller if I can identify the individual(s) concerned.</description>
      <pubDate>Mon, 04 Jun 2018 20:10:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Force-re-tried-items/m-p/78230#M30279</guid>
      <dc:creator>NeilPannett</dc:creator>
      <dc:date>2018-06-04T20:10:00Z</dc:date>
    </item>
    <item>
      <title>Check the audit log in…</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Force-re-tried-items/m-p/78231#M30280</link>
      <description>Check the audit log in System, it might be in there.</description>
      <pubDate>Mon, 04 Jun 2018 22:57:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Force-re-tried-items/m-p/78231#M30280</guid>
      <dc:creator>John__Carter</dc:creator>
      <dc:date>2018-06-04T22:57:00Z</dc:date>
    </item>
    <item>
      <title>Ah - so it is.
Thanks John</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Force-re-tried-items/m-p/78232#M30281</link>
      <description>Ah - so it is.
Thanks John</description>
      <pubDate>Wed, 06 Jun 2018 01:54:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Force-re-tried-items/m-p/78232#M30281</guid>
      <dc:creator>NeilPannett</dc:creator>
      <dc:date>2018-06-06T01:54:00Z</dc:date>
    </item>
  </channel>
</rss>

