<?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 There needs to be a delay in… in Product Forum</title>
    <link>https://community.blueprism.com/t5/Product-Forum/Process-with-quot-Pending-quot-status-on-schedule/m-p/59914#M13467</link>
    <description>There needs to be a delay in your schedules between the Resource Machine going from a 'Login Agent' stage (blue key icon in the control room) and the 'Runtime Resource' state.&amp;nbsp; Unfortunately, the current schedule design in Blue Prism necessitates 2 schedules to achieve this:&amp;nbsp;
&amp;nbsp; 1. Schedule to run the Log In process
&amp;nbsp; 2. Schedule a few minutes later to run the other Processes
We typically set Schedule 2 to run 2-5 minutes after schedule 1
&amp;nbsp;
The other issue you could be running in to is that you're not providing any necessary Input parameters in your schedule's task</description>
    <pubDate>Thu, 14 Jun 2018 21:55:00 GMT</pubDate>
    <dc:creator>ryanamiller</dc:creator>
    <dc:date>2018-06-14T21:55:00Z</dc:date>
    <item>
      <title>Process with "Pending" status on schedule</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Process-with-quot-Pending-quot-status-on-schedule/m-p/59913#M13466</link>
      <description>I€™m having some problems with the scheduler in BP.

&amp;nbsp;

I configure a schedule in BP with 5 process to run one after other, at 7 pm for example. The first process (Login from Login Agent object) run and finished with €œCompleted€&amp;#157; status. After that, the second process to run stays with €œPending€&amp;#157; status and the schedule stays waiting for a manual action.

&amp;nbsp;

Can you help me to understand why the second process does not run automatically?

&amp;nbsp;

Note: if I click on the second process and select €œstart€&amp;#157; option the process run and the schedule continue working normally.</description>
      <pubDate>Wed, 13 Jun 2018 20:25:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Process-with-quot-Pending-quot-status-on-schedule/m-p/59913#M13466</guid>
      <dc:creator>RaúlHernández</dc:creator>
      <dc:date>2018-06-13T20:25:00Z</dc:date>
    </item>
    <item>
      <title>There needs to be a delay in…</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Process-with-quot-Pending-quot-status-on-schedule/m-p/59914#M13467</link>
      <description>There needs to be a delay in your schedules between the Resource Machine going from a 'Login Agent' stage (blue key icon in the control room) and the 'Runtime Resource' state.&amp;nbsp; Unfortunately, the current schedule design in Blue Prism necessitates 2 schedules to achieve this:&amp;nbsp;
&amp;nbsp; 1. Schedule to run the Log In process
&amp;nbsp; 2. Schedule a few minutes later to run the other Processes
We typically set Schedule 2 to run 2-5 minutes after schedule 1
&amp;nbsp;
The other issue you could be running in to is that you're not providing any necessary Input parameters in your schedule's task</description>
      <pubDate>Thu, 14 Jun 2018 21:55:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Process-with-quot-Pending-quot-status-on-schedule/m-p/59914#M13467</guid>
      <dc:creator>ryanamiller</dc:creator>
      <dc:date>2018-06-14T21:55:00Z</dc:date>
    </item>
    <item>
      <title>Ryan has answered this well…</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Process-with-quot-Pending-quot-status-on-schedule/m-p/59915#M13468</link>
      <description>Ryan has answered this well. A pause between tasks option on the Schedule would be useful - although you could achieve the same with a simple Blue Prism process that sleeps for 5 minutes after the Login&amp;nbsp;and incorporate that into the schedule if you didn't want 2 separate schedules.&amp;nbsp;</description>
      <pubDate>Fri, 15 Jun 2018 13:06:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Process-with-quot-Pending-quot-status-on-schedule/m-p/59915#M13468</guid>
      <dc:creator>NicholasBell1</dc:creator>
      <dc:date>2018-06-15T13:06:00Z</dc:date>
    </item>
    <item>
      <title>Actually, we run this very…</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Process-with-quot-Pending-quot-status-on-schedule/m-p/59916#M13469</link>
      <description>Actually, we run this very well in our organisation.&amp;nbsp; You need to make sure for the second (and subsequent) scheduled processes in the schedule that the next process is selected to start.&amp;nbsp; I have enclosed an image for this.&amp;nbsp; We also make sure that the ""Fail fast on any errors: box is deselected, as this causes the schedule to fail.&amp;nbsp; After the last scheduled process is run, choose ""Abort"" from the dropdown box to complete the schedule.</description>
      <pubDate>Thu, 21 Jun 2018 04:35:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Process-with-quot-Pending-quot-status-on-schedule/m-p/59916#M13469</guid>
      <dc:creator>DarrenO_Brien</dc:creator>
      <dc:date>2018-06-21T04:35:00Z</dc:date>
    </item>
  </channel>
</rss>

