<?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 Re: DEV 1 SCHEDULER SUCCESSFUL SAP PROCESS TEST SCHEDULER FAILURE PROCESS QUESTION in Product Forum</title>
    <link>https://community.blueprism.com/t5/Product-Forum/DEV-1-SCHEDULER-SUCCESSFUL-SAP-PROCESS-TEST-SCHEDULER-FAILURE/m-p/96410#M44692</link>
    <description>Hi Ebony you'll need to provide more detail for anyone to understand the problem. What does '&lt;SPAN&gt;mid way through the collection' mean? What does the session log say?&lt;/SPAN&gt;</description>
    <pubDate>Wed, 24 Mar 2021 15:44:18 GMT</pubDate>
    <dc:creator>John__Carter</dc:creator>
    <dc:date>2021-03-24T15:44:18Z</dc:date>
    <item>
      <title>DEV 1 SCHEDULER SUCCESSFUL SAP PROCESS TEST SCHEDULER FAILURE PROCESS QUESTION</title>
      <link>https://community.blueprism.com/t5/Product-Forum/DEV-1-SCHEDULER-SUCCESSFUL-SAP-PROCESS-TEST-SCHEDULER-FAILURE/m-p/96409#M44691</link>
      <description>​​Hello,&lt;BR /&gt;&lt;BR /&gt;A process runs successful in development in SAP. Then runs successfully on the development scheduler in SAP.&lt;BR /&gt;When the bot is migrated to test and scheduled it fails mid way through the going through the collection. What could be causing it to fail mid way through the collection if it did not have an issue initially with the same data in the collection from dev to test?​​&lt;BR /&gt;&lt;BR /&gt;There is a collection of 200 rows. The data is entered into SAP into the correct field from the spreadsheet by spying the binoculars and searching for the field name. &lt;BR /&gt;Why would the data enter correctly on 24/200 rows but then the BOT errors entering it in on the 24th row? The position binocular which searches for the field is in the same place.</description>
      <pubDate>Wed, 24 Mar 2021 11:27:53 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/DEV-1-SCHEDULER-SUCCESSFUL-SAP-PROCESS-TEST-SCHEDULER-FAILURE/m-p/96409#M44691</guid>
      <dc:creator>ehedgepeth1</dc:creator>
      <dc:date>2021-03-24T11:27:53Z</dc:date>
    </item>
    <item>
      <title>Re: DEV 1 SCHEDULER SUCCESSFUL SAP PROCESS TEST SCHEDULER FAILURE PROCESS QUESTION</title>
      <link>https://community.blueprism.com/t5/Product-Forum/DEV-1-SCHEDULER-SUCCESSFUL-SAP-PROCESS-TEST-SCHEDULER-FAILURE/m-p/96410#M44692</link>
      <description>Hi Ebony you'll need to provide more detail for anyone to understand the problem. What does '&lt;SPAN&gt;mid way through the collection' mean? What does the session log say?&lt;/SPAN&gt;</description>
      <pubDate>Wed, 24 Mar 2021 15:44:18 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/DEV-1-SCHEDULER-SUCCESSFUL-SAP-PROCESS-TEST-SCHEDULER-FAILURE/m-p/96410#M44692</guid>
      <dc:creator>John__Carter</dc:creator>
      <dc:date>2021-03-24T15:44:18Z</dc:date>
    </item>
    <item>
      <title>Re: DEV 1 SCHEDULER SUCCESSFUL SAP PROCESS TEST SCHEDULER FAILURE PROCESS QUESTION</title>
      <link>https://community.blueprism.com/t5/Product-Forum/DEV-1-SCHEDULER-SUCCESSFUL-SAP-PROCESS-TEST-SCHEDULER-FAILURE/m-p/96411#M44693</link>
      <description>​There is a collection of 200 rows. The data is entered into SAP into the correct field from the spreadsheet by spying the binoculars and searching for the field name. &lt;BR /&gt;Why would the data enter correctly on 24/200 rows but then the BOT errors entering it in on the 24th row? The position binocular which searches for the field is in the same place.</description>
      <pubDate>Wed, 24 Mar 2021 17:33:48 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/DEV-1-SCHEDULER-SUCCESSFUL-SAP-PROCESS-TEST-SCHEDULER-FAILURE/m-p/96411#M44693</guid>
      <dc:creator>ehedgepeth1</dc:creator>
      <dc:date>2021-03-24T17:33:48Z</dc:date>
    </item>
  </channel>
</rss>

