同步时间跨越与推送新实体时间的可能问题 [英] Possible Issue with Sync time cross over with Pushing new entities time

问题描述

大家好，

随着时间的推移，我们注意到一些实体在我们似乎从推送中获得了成功的响应后没有被同步回来。这有可能吗？我们已经检查了我们的同步代码，并且没有找到大多数实体同步的理由，而有些则没有.b $ b。我们在这些同步时没有发生错误，所以想问下列是否可行....

We have noticed over time that some entities are not getting synced back after we appear to have got a successful response from a push. Could this be possible? We have checked our sync code and can find no reason why the majority of entities would sync and some not. We have no errors occurring at the time of these syncs, so would like to ask whether the following is possible ....

示例

同步1发生在11.45.16am

Sync 1 happens at 11.45.16am

推出新实体，比如新的关键字，在12：00.06pm

New entities are pushed, say new keywords, at 12.00.06pm

同步2发生在12：00.07pm并且请求数据回到11.45.16am

Sync 2 happens at 12.00.07pm and requests data back to 11.45.16am

同步3发生并请求数据从12.15.18pm返回到12.00.07pm

Sync 3 happens and requests data from 12.15.18pm back to 12.00.07pm

是否有可能同步12.00.07pm没有得到所有在12.00.06推送的项目，因为他们仍然在Bing以某种方式处理，但它们实际上是时间戳，因为已经在下午12点00分收到了。也许我们在同步2中只获得了4000个5000个关键字
。因此，我们的同步在时间上向前移动，从未真正同步这些关键字

Is it possible that the sync at 12.00.07pm doesn't get all of the items pushed at 12.00.06 as they are still being processed somehow at Bing, but they are actually timestamped as having been received at 12.00.06pm. Maybe we only got 4000 of 5000 keywords back on sync 2. And that because of this, our sync as it moves forward in time, never actually syncs those keywords

非常感谢提前

Giles Bodger

Giles Bodger

推荐答案

嗨Giles。

Hi Giles.

请确认，您使用的是先前下载的同步时间值，还是使用本地生成的DateTime值？作为最佳实践，我们建议您使用下载文件中的同步时间。按照这种做法，您不应该在后续同步中观察到
缺失的数据。有关详细信息，请参阅
DownloadCampaignsByCampaignIds 和  下载和上传广告系列 例如" Set
  LastSyncTimeInUTC   element $ b前一次下载时间戳的请求$ b仅请求自上次下载以来已更新或删除的实体。"

Please confirm, are you using the Sync Time value from a previous download, or are you using a locally generated DateTime value? As a best practice we recommend that you use the Sync Time from the download file. Following this practice you should not observe missing data on subsequent syncs. For more information, please see DownloadCampaignsByCampaignIds and Downloading and Uploading Campaigns e.g. "Set the LastSyncTimeInUTC element of the request to the time stamp of the previous download to request only those entities that have been updated or deleted since the last download."

祝你好运，

Eric

这篇关于同步时间跨越与推送新实体时间的可能问题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！