<?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 Daylight Savings Time - 2 a.m. Did Not Exist This Morning - Schedule Impact in Product Forum</title>
    <link>https://community.blueprism.com/t5/Product-Forum/Daylight-Savings-Time-2-a-m-Did-Not-Exist-This-Morning-Schedule/m-p/61745#M15001</link>
    <description>&lt;P style="margin: 0in; font-family: 'Segoe UI'; font-size: 10.5pt;"&gt;2 a.m. EST did not exist this morning -- app server Event Log shows Blue Prism does not show any events in the 2 a.m. hour.&amp;nbsp; &amp;nbsp;Time changed from 2 a.m. to 3 a.m. and depending on your Scheduler - Resilience setting, schedules in the 2 a.m. hour were never run.&amp;nbsp;&amp;nbsp; We have a 15 minute Scheduler - Resilience setting and so any schedule run between 2 a.m. and 2:44&amp;nbsp;a.m. was not run.&amp;nbsp; &amp;nbsp; Due to the 15 minute Resilience setting, 2:45 a.m. to 2:59 a.m. schedules were picked up at 3 a.m. to run.&amp;nbsp; &amp;nbsp;There was no important schedule designated to run in the 2 a.m. - 2:44&amp;nbsp;a.m. time frame and so nothing important was missed for us but&amp;nbsp;this is just an interesting "issue" to be aware of for next year in case we schedule important things to run at 2 a.m.&amp;nbsp;&amp;nbsp;&amp;nbsp; I know that updating the Resilience setting to 1 hour could seem like a good idea but if something needs to run within a timeframe, that could cause things to run after that window and so updating the setting beyond 15 minutes doesn't seem good just to overcome an issue that happens once a year.&amp;nbsp;&amp;nbsp; Also, I wonder about what happens in the Fall and if schedules at 2 a.m. may try to run twice.&amp;nbsp;&amp;nbsp; Anyway, this is kind of funny and scary at the same.&amp;nbsp;&amp;nbsp;&amp;nbsp; I wonder what impact this had on others and I wonder how others may alert themselves if something should have run during a window of time and Blue Prism doesn't even have any display of the schedule in the Recent Activity nor any Session created in that window.&amp;nbsp;&amp;nbsp;&amp;nbsp; I have things query the database for run terminations, "schedule - resource offline" issues, missing resources, pending sessions, long running sessions, sessions in the Warning status (no stage update in over 5 minutes), etc. to send my team email alerts but if Blue Prism does not even try to run a process/schedule and nothing is even in the Event Log, this is an interesting thing to look for...thoughts?&lt;/P&gt;&lt;BR /&gt;&lt;BR /&gt;------------------------------&lt;BR /&gt;Brenton Westwood&lt;BR /&gt;Systems Analyst&lt;BR /&gt;Southern Company&lt;BR /&gt;------------------------------&lt;BR /&gt;</description>
    <pubDate>Sun, 08 Mar 2020 18:15:00 GMT</pubDate>
    <dc:creator>bjwestwo</dc:creator>
    <dc:date>2020-03-08T18:15:00Z</dc:date>
    <item>
      <title>Daylight Savings Time - 2 a.m. Did Not Exist This Morning - Schedule Impact</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Daylight-Savings-Time-2-a-m-Did-Not-Exist-This-Morning-Schedule/m-p/61745#M15001</link>
      <description>&lt;P style="margin: 0in; font-family: 'Segoe UI'; font-size: 10.5pt;"&gt;2 a.m. EST did not exist this morning -- app server Event Log shows Blue Prism does not show any events in the 2 a.m. hour.&amp;nbsp; &amp;nbsp;Time changed from 2 a.m. to 3 a.m. and depending on your Scheduler - Resilience setting, schedules in the 2 a.m. hour were never run.&amp;nbsp;&amp;nbsp; We have a 15 minute Scheduler - Resilience setting and so any schedule run between 2 a.m. and 2:44&amp;nbsp;a.m. was not run.&amp;nbsp; &amp;nbsp; Due to the 15 minute Resilience setting, 2:45 a.m. to 2:59 a.m. schedules were picked up at 3 a.m. to run.&amp;nbsp; &amp;nbsp;There was no important schedule designated to run in the 2 a.m. - 2:44&amp;nbsp;a.m. time frame and so nothing important was missed for us but&amp;nbsp;this is just an interesting "issue" to be aware of for next year in case we schedule important things to run at 2 a.m.&amp;nbsp;&amp;nbsp;&amp;nbsp; I know that updating the Resilience setting to 1 hour could seem like a good idea but if something needs to run within a timeframe, that could cause things to run after that window and so updating the setting beyond 15 minutes doesn't seem good just to overcome an issue that happens once a year.&amp;nbsp;&amp;nbsp; Also, I wonder about what happens in the Fall and if schedules at 2 a.m. may try to run twice.&amp;nbsp;&amp;nbsp; Anyway, this is kind of funny and scary at the same.&amp;nbsp;&amp;nbsp;&amp;nbsp; I wonder what impact this had on others and I wonder how others may alert themselves if something should have run during a window of time and Blue Prism doesn't even have any display of the schedule in the Recent Activity nor any Session created in that window.&amp;nbsp;&amp;nbsp;&amp;nbsp; I have things query the database for run terminations, "schedule - resource offline" issues, missing resources, pending sessions, long running sessions, sessions in the Warning status (no stage update in over 5 minutes), etc. to send my team email alerts but if Blue Prism does not even try to run a process/schedule and nothing is even in the Event Log, this is an interesting thing to look for...thoughts?&lt;/P&gt;&lt;BR /&gt;&lt;BR /&gt;------------------------------&lt;BR /&gt;Brenton Westwood&lt;BR /&gt;Systems Analyst&lt;BR /&gt;Southern Company&lt;BR /&gt;------------------------------&lt;BR /&gt;</description>
      <pubDate>Sun, 08 Mar 2020 18:15:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Daylight-Savings-Time-2-a-m-Did-Not-Exist-This-Morning-Schedule/m-p/61745#M15001</guid>
      <dc:creator>bjwestwo</dc:creator>
      <dc:date>2020-03-08T18:15:00Z</dc:date>
    </item>
  </channel>
</rss>

