<?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 You should be able to trace in Product Forum</title>
    <link>https://community.blueprism.com/t5/Product-Forum/Scheduler-not-working-properly/m-p/77745#M29876</link>
    <description>You should be able to trace the fault via various log files available to you: Session Logs, Schedular Logs, and the Windows Event Logs on the Application Server.
One thing to remember is the network connection needs to be in place and the resource available on the Application Server machine that starts the schedules - the connection from your local machine to the resource is not relivant.</description>
    <pubDate>Thu, 24 Aug 2017 17:44:00 GMT</pubDate>
    <dc:creator>Denis__Dennehy</dc:creator>
    <dc:date>2017-08-24T17:44:00Z</dc:date>
    <item>
      <title>Scheduler not working properly</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Scheduler-not-working-properly/m-p/77744#M29875</link>
      <description>Issue - Blue prism scheduler is not working as per schedule designed.

Issue Details - For one process we have designed scheduler some processes on particular VMs but sometimes it happens that it didn't run any of the process on particular VMs. In this scenario we had to run these VMs manually.

Can we have any resolution or guidelines for this?</description>
      <pubDate>Thu, 24 Aug 2017 14:23:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Scheduler-not-working-properly/m-p/77744#M29875</guid>
      <dc:creator>AMITJAGTAP1</dc:creator>
      <dc:date>2017-08-24T14:23:00Z</dc:date>
    </item>
    <item>
      <title>You should be able to trace</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Scheduler-not-working-properly/m-p/77745#M29876</link>
      <description>You should be able to trace the fault via various log files available to you: Session Logs, Schedular Logs, and the Windows Event Logs on the Application Server.
One thing to remember is the network connection needs to be in place and the resource available on the Application Server machine that starts the schedules - the connection from your local machine to the resource is not relivant.</description>
      <pubDate>Thu, 24 Aug 2017 17:44:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Scheduler-not-working-properly/m-p/77745#M29876</guid>
      <dc:creator>Denis__Dennehy</dc:creator>
      <dc:date>2017-08-24T17:44:00Z</dc:date>
    </item>
    <item>
      <title>I would recommend checking if</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Scheduler-not-working-properly/m-p/77746#M29877</link>
      <description>I would recommend checking if there are any hung processes in a ""stopping"" state in the control room for the particular runtime resource your experiencing issues with. If you have processes that are in a stopping state, it will need to be cleared by running the following query against your Blue Prism database:
declare @now datetime
set @now = getdate()
update bpasession set enddatetime = @now, stoprequested = null, statusid= 3 where sessionnumber = Session_Number_From_Blue_Prism</description>
      <pubDate>Mon, 28 Aug 2017 04:55:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Scheduler-not-working-properly/m-p/77746#M29877</guid>
      <dc:creator>BryanRego</dc:creator>
      <dc:date>2017-08-28T04:55:00Z</dc:date>
    </item>
    <item>
      <title>I would recommend checking if</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Scheduler-not-working-properly/m-p/77747#M29878</link>
      <description>I would recommend checking if there are any hung processes in a ""stopping"" state in the control room for the particular runtime resource your experiencing issues with. If you have processes that are in a stopping state, it will need to be cleared by running the following query against your Blue Prism database:
declare @now datetime
set @now = getdate()
update bpasession set enddatetime = @now, stoprequested = null, statusid= 3 where sessionnumber = Session_Number_From_Blue_Prism</description>
      <pubDate>Mon, 28 Aug 2017 04:56:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Scheduler-not-working-properly/m-p/77747#M29878</guid>
      <dc:creator>BryanRego</dc:creator>
      <dc:date>2017-08-28T04:56:00Z</dc:date>
    </item>
  </channel>
</rss>

