Invalid timestamp
Stay organized with collections
Save and categorize content based on your preferences.
Description
An invalid timestamp issue occurs when a review
or merchant
contains
a create_timestamp
or last_update_timestamp
that is invalid or when create_timestamp
is after last_update_timestamp
.
How to fix
Deliver the review
or merchant
ensuring that create_timestamp
and last_update_timestamp
are valid.
Example
On March 1st, you upload the feed file "2017_03_01.xml" to your endpoint. The file contains the
following contents:
<merchant id="2739">
<name>Google Store</name>
<merchant_url>http://store.google.com</merchant_url>
<rating_url>http://www.example-reviews.com/m2739.html</rating_url>
<create_timestamp> 2017-02-25T03:02:23Z
</create_timestamp>
<last_update_timestamp> 2017-02-25T03:01:32Z
</last_update_timestamp>
</merchant>
The above file contains a merchant
entry whose create_timestamp
is after last_update_timestamp
. After
processing your feed, the support team notifies you that a data issue, invalid timestamp, has occurred.
A few days later, after reviewing the documentation, you upload the file "2017_03_04-fix.xml"
to your endpoint to resolve the invalid rating issue:
<merchant id="2739">
<name>Google Store</name>
<merchant_url>http://store.google.com</merchant_url>
<rating_url>http://www.example-reviews.com/m2739.html</rating_url>
<create_timestamp> 2017-02-25T03:02:23Z
</create_timestamp>
<last_update_timestamp> 2017-02-25T03:02:23Z
</last_update_timestamp>
</merchant>
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License
, and code samples are licensed under the Apache 2.0 License
. For details, see the Google Developers Site Policies
. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2023-08-11 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2023-08-11 UTC."],[[["\u003cp\u003eInvalid timestamps occur when a \u003ccode\u003ereview\u003c/code\u003e or \u003ccode\u003emerchant\u003c/code\u003e contains an invalid \u003ccode\u003ecreate_timestamp\u003c/code\u003e or \u003ccode\u003elast_update_timestamp\u003c/code\u003e, or when \u003ccode\u003ecreate_timestamp\u003c/code\u003e is after \u003ccode\u003elast_update_timestamp\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eTo fix invalid timestamps, ensure that both \u003ccode\u003ecreate_timestamp\u003c/code\u003e and \u003ccode\u003elast_update_timestamp\u003c/code\u003e are valid and that \u003ccode\u003ecreate_timestamp\u003c/code\u003e is not after \u003ccode\u003elast_update_timestamp\u003c/code\u003e within your \u003ccode\u003ereview\u003c/code\u003e or \u003ccode\u003emerchant\u003c/code\u003e data.\u003c/p\u003e\n"],["\u003cp\u003eAn example of an invalid timestamp is when a \u003ccode\u003emerchant\u003c/code\u003e entry has a \u003ccode\u003ecreate_timestamp\u003c/code\u003e of "2017-02-25T03:02:23Z" and a \u003ccode\u003elast_update_timestamp\u003c/code\u003e of "2017-02-25T03:01:32Z", as the creation timestamp is after the update timestamp.\u003c/p\u003e\n"],["\u003cp\u003eResolving this issue requires correcting the timestamps, for instance, by setting both \u003ccode\u003ecreate_timestamp\u003c/code\u003e and \u003ccode\u003elast_update_timestamp\u003c/code\u003e to "2017-02-25T03:02:23Z" to ensure they are valid and chronologically consistent.\u003c/p\u003e\n"]]],[],null,["# Invalid timestamp\n\nDescription\n-----------\n\nAn invalid timestamp issue occurs when a [`review`](/merchant-review-feeds/xmlschema#\u003creview\u003e)\nor [`merchant`](/merchant-review-feeds/xmlschema#\u003cmerchant\u003e) contains\na `create_timestamp` or `last_update_timestamp` that is invalid or when\n`create_timestamp` is after `last_update_timestamp`.\n\nHow to fix\n----------\n\nDeliver the [`review`](/merchant-review-feeds/xmlschema#\u003creview\u003e) or\n[`merchant`](/merchant-review-feeds/xmlschema#\u003cmerchant\u003e) ensuring that\n`create_timestamp` and `last_update_timestamp` are valid.\n\nExample\n-------\n\nOn March 1st, you upload the feed file \"2017_03_01.xml\" to your endpoint. The file contains the\nfollowing contents: \n\n```scdoc\n\u003cmerchant id=\"2739\"\u003e\n \u003cname\u003eGoogle Store\u003c/name\u003e\n \u003cmerchant_url\u003ehttp://store.google.com\u003c/merchant_url\u003e\n \u003crating_url\u003ehttp://www.example-reviews.com/m2739.html\u003c/rating_url\u003e\n \u003ccreate_timestamp\u003e2017-02-25T03:02:23Z\u003c/create_timestamp\u003e\n \u003clast_update_timestamp\u003e2017-02-25T03:01:32Z\u003c/last_update_timestamp\u003e\n\u003c/merchant\u003e\n```\n\nThe above file contains a [`merchant`](/merchant-review-feeds/xmlschema#\u003cmerchant\u003e)\nentry whose `create_timestamp` is after `last_update_timestamp`. After\nprocessing your feed, the support team notifies you that a data issue, invalid timestamp, has occurred.\n\nA few days later, after reviewing the documentation, you upload the file \"2017_03_04-fix.xml\"\nto your endpoint to resolve the invalid rating issue: \n\n```scdoc\n\u003cmerchant id=\"2739\"\u003e\n \u003cname\u003eGoogle Store\u003c/name\u003e\n \u003cmerchant_url\u003ehttp://store.google.com\u003c/merchant_url\u003e\n \u003crating_url\u003ehttp://www.example-reviews.com/m2739.html\u003c/rating_url\u003e\n \u003ccreate_timestamp\u003e2017-02-25T03:02:23Z\u003c/create_timestamp\u003e\n \u003clast_update_timestamp\u003e2017-02-25T03:02:23Z\u003c/last_update_timestamp\u003e\n\u003c/merchant\u003e\n```"]]
