<?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 Schedule Monitor working incorrectly after upgrading to Blue Prism 7.4.1 in Digital Exchange</title>
    <link>https://community.blueprism.com/t5/Digital-Exchange/Schedule-Monitor-working-incorrectly-after-upgrading-to-Blue/m-p/125239#M4671</link>
    <description>&lt;P&gt;Hi, we’ve been experiencing some issues with the Schedule Monitor after migrating from Blue Prism 6.10.4 to Blue Prism 7.4.1.&lt;/P&gt;&lt;P&gt;What we noticed is that it only detects schedules that overlapped, but not the ones that never started or the ones that failed during execution. I assume this is because, in the newer version, there must have been some change in how records are stored in the database, which causes these scenarios not to be detected.&lt;/P&gt;&lt;P&gt;Has anyone found a workaround or does anyone have a more up-to-date version of this application? I’m sharing the link to the Digital Exchange asset here:&amp;nbsp;&lt;A href="https://digitalexchange.blueprism.com/cardDetails?id=124010" target="_blank"&gt;https://digitalexchange.blueprism.com/cardDetails?id=124010&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;</description>
    <pubDate>Wed, 08 Apr 2026 12:53:31 GMT</pubDate>
    <dc:creator>eugenio.punti</dc:creator>
    <dc:date>2026-04-08T12:53:31Z</dc:date>
    <item>
      <title>Schedule Monitor working incorrectly after upgrading to Blue Prism 7.4.1</title>
      <link>https://community.blueprism.com/t5/Digital-Exchange/Schedule-Monitor-working-incorrectly-after-upgrading-to-Blue/m-p/125239#M4671</link>
      <description>&lt;P&gt;Hi, we’ve been experiencing some issues with the Schedule Monitor after migrating from Blue Prism 6.10.4 to Blue Prism 7.4.1.&lt;/P&gt;&lt;P&gt;What we noticed is that it only detects schedules that overlapped, but not the ones that never started or the ones that failed during execution. I assume this is because, in the newer version, there must have been some change in how records are stored in the database, which causes these scenarios not to be detected.&lt;/P&gt;&lt;P&gt;Has anyone found a workaround or does anyone have a more up-to-date version of this application? I’m sharing the link to the Digital Exchange asset here:&amp;nbsp;&lt;A href="https://digitalexchange.blueprism.com/cardDetails?id=124010" target="_blank"&gt;https://digitalexchange.blueprism.com/cardDetails?id=124010&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;</description>
      <pubDate>Wed, 08 Apr 2026 12:53:31 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Digital-Exchange/Schedule-Monitor-working-incorrectly-after-upgrading-to-Blue/m-p/125239#M4671</guid>
      <dc:creator>eugenio.punti</dc:creator>
      <dc:date>2026-04-08T12:53:31Z</dc:date>
    </item>
  </channel>
</rss>

