Very interesting. At least if fits with my deepest darkest suspicions. :) It might be possible for us to use a custom item to avoid this rejection and/or delay. I don't believe the items ever show up so delay isn't likely to be happening in our case.
And you're quite right, as usual, in that we will most assuredly be back to square one eventually if we neither use a custom item type nor randomize our content. What we find irksome is that we get a return status of 201. Doesn't that seem like a bug to you? On Jan 7, 12:39 am, Celebird <[email protected]> wrote: > if the same items are being submitted with different ids -- > or some or another same similar products rules issue -- > within the products item-type the items may be triggering > a disapproval or a long approval process. > > creating a new account may be simply delaying the time > when the approval process or event is triggered yet again. > > if current inserts are using the products item-type > try using a custom item-type for most all testing -- > the products item-type may not process as deftly > as other item-types given the approval process and > migration to google-product-search that's not a part > of other item-types. > > also, regardless of approval status, if the same item data > is processed too quickly there is an indexing delay within > the products item-type and dashboard; that is, i've had it > take a day to fully process products item-type changes > that did affect subsequent inserts -- which adheres to > how i read the documentation for the products item-type. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Base Data API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Base-data-API?hl=en -~----------~----~----~----~------~----~------~--~---
