<?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 We have exactly the same in Product Forum</title>
    <link>https://community.blueprism.com/t5/Product-Forum/My-Schedule-Won-t-Run/m-p/64291#M17094</link>
    <description>We have exactly the same problem and I don't know what's stopping it (and would really know it). Workaround used is:
1. Set up schedule
2. Check if process running manually (run process from Session manager)
3. Restart BluePrism server
And it works, pretty much 100% of the time.</description>
    <pubDate>Mon, 07 Aug 2017 12:28:00 GMT</pubDate>
    <dc:creator>Martynas</dc:creator>
    <dc:date>2017-08-07T12:28:00Z</dc:date>
    <item>
      <title>My Schedule Won't Run</title>
      <link>https://community.blueprism.com/t5/Product-Forum/My-Schedule-Won-t-Run/m-p/64290#M17093</link>
      <description>Hi

I've set up a schedule in our Production environment (v5.0.30) to run a process every 2 hours between 08:00 and 20:00.

The resource PC on the machine is connected ok, but the process doesn't run at 08:00 or 10:00 or 12:00 or... 

If I try and start the schedule manually, it doesn't do anything either.

Nothing is shown in the Process - Audit Logs either.

But, if I manually run the process from Session Manager, it works.

What could be stopping the schedule from running ?

Thanks
Graeme</description>
      <pubDate>Mon, 07 Aug 2017 12:18:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/My-Schedule-Won-t-Run/m-p/64290#M17093</guid>
      <dc:creator>Graeme__Tacon</dc:creator>
      <dc:date>2017-08-07T12:18:00Z</dc:date>
    </item>
    <item>
      <title>We have exactly the same</title>
      <link>https://community.blueprism.com/t5/Product-Forum/My-Schedule-Won-t-Run/m-p/64291#M17094</link>
      <description>We have exactly the same problem and I don't know what's stopping it (and would really know it). Workaround used is:
1. Set up schedule
2. Check if process running manually (run process from Session manager)
3. Restart BluePrism server
And it works, pretty much 100% of the time.</description>
      <pubDate>Mon, 07 Aug 2017 12:28:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/My-Schedule-Won-t-Run/m-p/64291#M17094</guid>
      <dc:creator>Martynas</dc:creator>
      <dc:date>2017-08-07T12:28:00Z</dc:date>
    </item>
    <item>
      <title>I've just retired and</title>
      <link>https://community.blueprism.com/t5/Product-Forum/My-Schedule-Won-t-Run/m-p/64292#M17095</link>
      <description>I've just retired and unretired the resource in Resource Management and the 10:00 schedule ran automatically.</description>
      <pubDate>Mon, 07 Aug 2017 14:03:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/My-Schedule-Won-t-Run/m-p/64292#M17095</guid>
      <dc:creator>Graeme__Tacon</dc:creator>
      <dc:date>2017-08-07T14:03:00Z</dc:date>
    </item>
    <item>
      <title>There is a fundamental</title>
      <link>https://community.blueprism.com/t5/Product-Forum/My-Schedule-Won-t-Run/m-p/64293#M17096</link>
      <description>There is a fundamental difference between starting a session manually and starting it by scheular - so doing one in no way tests that the other will work.
Starting a session manually is direct communication between your own locally installed Blue Prism client and the remote resource pc - if that works you are only prooving that you can directly connect with the resourcepc - you are not prooving that the application server (from where schedules are kicked off) can communicate with the resourcepc.</description>
      <pubDate>Tue, 08 Aug 2017 14:33:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/My-Schedule-Won-t-Run/m-p/64293#M17096</guid>
      <dc:creator>Denis__Dennehy</dc:creator>
      <dc:date>2017-08-08T14:33:00Z</dc:date>
    </item>
  </channel>
</rss>

