<?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 Scheduler Not Working For Short Periods in Product Forum</title>
    <link>https://community.blueprism.com/t5/Product-Forum/Scheduler-Not-Working-For-Short-Periods/m-p/54236#M8790</link>
    <description>Hello,&lt;BR /&gt;We've seen an issue a few times in the past week where the scheduler seems to just not schedule a process.&amp;nbsp; We have a process that runs every 5 minutes.&amp;nbsp; Yesterday, it finished one process at 2:37PM and then did not schedule the process again until 3:11PM.&amp;nbsp; It's like it gave the BOT a little break.&lt;BR /&gt;&lt;BR /&gt;We have one license per resource machine and we only run one process at a time on each resource.&amp;nbsp; It doesn't seem like it could be a licensing issue. We have automatic archiving running, but it is not running on the BOT that had the issue yesterday.&lt;BR /&gt;&lt;BR /&gt;Anyone have suggestions as to what this could be and how to fix it?&amp;nbsp; &lt;BR /&gt;&lt;BR /&gt;Thanks.&lt;BR /&gt;Tracy ​&lt;BR /&gt;&lt;BR /&gt;------------------------------&lt;BR /&gt;Tracy Green&lt;BR /&gt;Systems Developer III&lt;BR /&gt;Federated Insurance&lt;BR /&gt;America/Chicago&lt;BR /&gt;------------------------------&lt;BR /&gt;</description>
    <pubDate>Tue, 03 Nov 2020 14:12:00 GMT</pubDate>
    <dc:creator>TracyGreen</dc:creator>
    <dc:date>2020-11-03T14:12:00Z</dc:date>
    <item>
      <title>Scheduler Not Working For Short Periods</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Scheduler-Not-Working-For-Short-Periods/m-p/54236#M8790</link>
      <description>Hello,&lt;BR /&gt;We've seen an issue a few times in the past week where the scheduler seems to just not schedule a process.&amp;nbsp; We have a process that runs every 5 minutes.&amp;nbsp; Yesterday, it finished one process at 2:37PM and then did not schedule the process again until 3:11PM.&amp;nbsp; It's like it gave the BOT a little break.&lt;BR /&gt;&lt;BR /&gt;We have one license per resource machine and we only run one process at a time on each resource.&amp;nbsp; It doesn't seem like it could be a licensing issue. We have automatic archiving running, but it is not running on the BOT that had the issue yesterday.&lt;BR /&gt;&lt;BR /&gt;Anyone have suggestions as to what this could be and how to fix it?&amp;nbsp; &lt;BR /&gt;&lt;BR /&gt;Thanks.&lt;BR /&gt;Tracy ​&lt;BR /&gt;&lt;BR /&gt;------------------------------&lt;BR /&gt;Tracy Green&lt;BR /&gt;Systems Developer III&lt;BR /&gt;Federated Insurance&lt;BR /&gt;America/Chicago&lt;BR /&gt;------------------------------&lt;BR /&gt;</description>
      <pubDate>Tue, 03 Nov 2020 14:12:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Scheduler-Not-Working-For-Short-Periods/m-p/54236#M8790</guid>
      <dc:creator>TracyGreen</dc:creator>
      <dc:date>2020-11-03T14:12:00Z</dc:date>
    </item>
    <item>
      <title>RE: Scheduler Not Working For Short Periods</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Scheduler-Not-Working-For-Short-Periods/m-p/54237#M8791</link>
      <description>Hi Tracy,&amp;nbsp; could you describe how your scheduler has been configured to start processes?&amp;nbsp; &amp;nbsp;Why did you expect the process to start earlier than 3.11PM,&amp;nbsp; was it scheduled to start earlier?&amp;nbsp; What is the logic within your process to stop running at 2.37PM,&amp;nbsp; does it stop when it runs out of work?&amp;nbsp; &amp;nbsp; &lt;BR /&gt;If you think there is a problem with schedules not starting (rather than a question about how schedules are configured), then what do the schedule logs say,&amp;nbsp; and what do the windows event logs on the Application Server for the times schedules failed to start?&lt;BR /&gt;Is your robot only working one process all day, irrelevant of the amount of work there is - if that is the case than the process should not be configured to stop when work runs out but instead poll all day.&amp;nbsp; However,&amp;nbsp; if the robot working a single process all day is inefficient (because there is not enough work for the entire day),&amp;nbsp; then consider working the process once or twice a day only (SLAs permitting) and moving onto other tasks or looking at the Dynamic Scheduler solution on the portal for ideas about how to build a more efficiant solution based upon work and priorities.&lt;BR /&gt;&lt;BR /&gt;------------------------------&lt;BR /&gt;Denis Dennehy&lt;BR /&gt;Head of Customer Success, EMEA&lt;BR /&gt;Blue Prism Ltd&lt;BR /&gt;Europe/London&lt;BR /&gt;------------------------------&lt;BR /&gt;</description>
      <pubDate>Wed, 04 Nov 2020 10:26:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Scheduler-Not-Working-For-Short-Periods/m-p/54237#M8791</guid>
      <dc:creator>Denis__Dennehy</dc:creator>
      <dc:date>2020-11-04T10:26:00Z</dc:date>
    </item>
  </channel>
</rss>

