<?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: pre-prod sync errors in _Ask A Question for Item Management (IM)</title>
    <link>https://community.1worldsync.com/t5/Ask-A-Question-for-Item/pre-prod-sync-errors/m-p/4862#M1739</link>
    <description>&lt;P&gt;Hello and thank you for reaching out.&amp;nbsp; Can you try again to post a screen capture?&lt;/P&gt;</description>
    <pubDate>Mon, 12 Sep 2022 20:21:03 GMT</pubDate>
    <dc:creator>CommunityJedi22</dc:creator>
    <dc:date>2022-09-12T20:21:03Z</dc:date>
    <item>
      <title>pre-prod sync errors</title>
      <link>https://community.1worldsync.com/t5/Ask-A-Question-for-Item/pre-prod-sync-errors/m-p/4861#M1738</link>
      <description>&lt;P&gt;The last update to pre-prod appears to be generating numerous sync errors that are getting sent to our test system.&amp;nbsp; We did not send any AS/2 messages to trigger these.&lt;/P&gt;
&lt;P&gt;I would paste a view of the enormous work list but I don't seem to have permission.&amp;nbsp; It looks like 54 messages were generated in a short time.&lt;/P&gt;</description>
      <pubDate>Mon, 12 Sep 2022 20:15:23 GMT</pubDate>
      <guid>https://community.1worldsync.com/t5/Ask-A-Question-for-Item/pre-prod-sync-errors/m-p/4861#M1738</guid>
      <dc:creator>Food_Fiend</dc:creator>
      <dc:date>2022-09-12T20:15:23Z</dc:date>
    </item>
    <item>
      <title>Re: pre-prod sync errors</title>
      <link>https://community.1worldsync.com/t5/Ask-A-Question-for-Item/pre-prod-sync-errors/m-p/4862#M1739</link>
      <description>&lt;P&gt;Hello and thank you for reaching out.&amp;nbsp; Can you try again to post a screen capture?&lt;/P&gt;</description>
      <pubDate>Mon, 12 Sep 2022 20:21:03 GMT</pubDate>
      <guid>https://community.1worldsync.com/t5/Ask-A-Question-for-Item/pre-prod-sync-errors/m-p/4862#M1739</guid>
      <dc:creator>CommunityJedi22</dc:creator>
      <dc:date>2022-09-12T20:21:03Z</dc:date>
    </item>
    <item>
      <title>Re: pre-prod sync errors</title>
      <link>https://community.1worldsync.com/t5/Ask-A-Question-for-Item/pre-prod-sync-errors/m-p/4863#M1740</link>
      <description>&lt;P&gt;I guess I had to upload it rather than paste it.&amp;nbsp; For some reason it tried to sync to recipient 'training gln retailer'.&lt;/P&gt;</description>
      <pubDate>Mon, 12 Sep 2022 20:30:00 GMT</pubDate>
      <guid>https://community.1worldsync.com/t5/Ask-A-Question-for-Item/pre-prod-sync-errors/m-p/4863#M1740</guid>
      <dc:creator>Food_Fiend</dc:creator>
      <dc:date>2022-09-12T20:30:00Z</dc:date>
    </item>
    <item>
      <title>Re: pre-prod sync errors</title>
      <link>https://community.1worldsync.com/t5/Ask-A-Question-for-Item/pre-prod-sync-errors/m-p/4864#M1741</link>
      <description>&lt;P&gt;Thank you for those additional details.&amp;nbsp; It helps a lot.&amp;nbsp; It appears that all of the errors I see in your PP worklist are related to a test recipient we sometimes use, GLN&amp;nbsp;&lt;SPAN class="ng-star-inserted" title="7701115113021"&gt;7701115113021,&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="ng-star-inserted" title="TRAINING GLN RETAILER"&gt;TRAINING GLN RETAILER.&amp;nbsp; Perhaps our teams were using that in your initial setup and one of the updates this weekend triggered these errors.&amp;nbsp; Can you delete the publications for this recipient unless they are otherwise needed?&amp;nbsp; I apologize for any inconvenience as I am not sure why these errors triggered all of a sudden for you0.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 12 Sep 2022 20:39:30 GMT</pubDate>
      <guid>https://community.1worldsync.com/t5/Ask-A-Question-for-Item/pre-prod-sync-errors/m-p/4864#M1741</guid>
      <dc:creator>CommunityJedi22</dc:creator>
      <dc:date>2022-09-12T20:39:30Z</dc:date>
    </item>
  </channel>
</rss>

