생성 시간 변경 문제는 업데이트 간에 review 또는 merchant의 생성 시간이 서로 다른 경우에 발생합니다. 생성 시간은 변경할 수 없는 필드이므로 생성 시간을 변경하면 이 문제가 발생합니다.
해결 방법
다음 옵션 중 하나를 선택하여 문제를 해결하세요.
옵션 A:
원래 생성 시간을 사용하려면 원래 create_timestamp 및 업데이트된 last_update_timestamp를 사용하여 review 또는 merchant를 다시 전송하세요.
옵션 B:
새 생성 시간을 사용하려면 새 create_timestamp 및 업데이트된 last_update_timestamp로 review 또는 merchant을 다시 전송하세요. 그런 다음 항목이 포함된 파일 이름을 지원팀에 알립니다. 지원팀에서 이 문제를 해결하는 데 도움을 드릴 수 있습니다.
예
3월 1일에 피드 파일 '2017_03_01.xml'을 엔드포인트에 업로드합니다. 파일에 이전에 전송되지 않은 리뷰 항목이 포함되어 있습니다.
<review id="156368" mid="2739">
<reviewer_name>Ada</reviewer_name>
<create_timestamp>2017-02-25T03:02:23Z</create_timestamp>
<last_update_timestamp>2017-02-25T03:02:23Z</last_update_timestamp>
<country_code>US</country_code>
<title>Great prices</title>
<content>My order arrived on time and I got a great price.</content>
<ratings>
<overall min="1" max="10">9</overall>
<customer_service min="1" max="10">10</customer_service>
</ratings>
<collection_method>after_fulfillment</collection_method>
</review>
다음 날 리뷰 '156368'의 생성 시간을 업데이트하는 다음 피드 파일 '2017_03_02.xml'을 제공합니다.
<review id="156368" mid="2739>
<reviewer_name>Ada</reviewer_name>
<create_timestamp>2017-02-26T11:01:42Z</create_timestamp>
<last_update_timestamp>2017-02-26T11:01:42Z</last_update_timestamp>
<country_code>US</country_code>
<title>Great prices!</title>
<content>My order arrived on time and I got a great price.</content>
<ratings>
<overall min="1" max="10">9</overall>
<customer_service min="1" max="10">10</customer_service>
</ratings>
<collection_method>after_fulfillment</collection_method>
</review>
리뷰 '156368'의 두 번째 항목은 생성 시간에 충돌을 일으킵니다. 데이터 문제가 발생했음을 알리는 지원팀의 알림이 전송됩니다.
이 문제를 해결하는 방법을 설명하는 문서를 검토한 후 생성 시간을 원래대로 변경하기 위해 옵션 A를 선택합니다.
원래 생성 시간은 '2017-02-25T03:02:23Z'이므로 3월 10일에 다음 피드 파일 '2017_03_10-fix.xml'을 제공합니다.
<review id="156368" mid="2739">
<reviewer_name>Ada</reviewer_name>
<create_timestamp>2017-02-25T03:02:23Z</create_timestamp>
<last_update_timestamp>2017-03-09T02:40:23Z</last_update_timestamp>
<country_code>US</country_code>
<title>Great prices!</title>
<content>My order arrived on time and I got a great price.</content>
<ratings>
<overall min="1" max="10>9</overall>
<customer_service min="1" max="10">10</customer_service>
</ratings>
<collection_method>after_fulfillment</collection_method>
</review>
[null,null,["최종 업데이트: 2025-07-26(UTC)"],[[["\u003cp\u003eA create time changed issue arises when the \u003ccode\u003ecreate_timestamp\u003c/code\u003e for a review or merchant is altered in subsequent updates, despite being an immutable field.\u003c/p\u003e\n"],["\u003cp\u003eThis issue differs from a conflicting update, where the \u003ccode\u003ecreate_timestamp\u003c/code\u003e changes but the \u003ccode\u003elast_update_timestamp\u003c/code\u003e remains the same.\u003c/p\u003e\n"],["\u003cp\u003eTo resolve this, either re-deliver the data with the original \u003ccode\u003ecreate_timestamp\u003c/code\u003e and an updated \u003ccode\u003elast_update_timestamp\u003c/code\u003e (Option A), or re-deliver with a new \u003ccode\u003ecreate_timestamp\u003c/code\u003e, updated \u003ccode\u003elast_update_timestamp\u003c/code\u003e, and notify the support team (Option B).\u003c/p\u003e\n"],["\u003cp\u003eAn example scenario illustrates how updating a review's \u003ccode\u003ecreate_timestamp\u003c/code\u003e in a subsequent feed file can lead to a create time changed issue, requiring correction using one of the provided options.\u003c/p\u003e\n"]]],[],null,["# Create time changed\n\nDescription\n-----------\n\nA create time changed issue occurs when a [`review`](/merchant-review-feeds/xmlschema#\u003creview\u003e)\nor [`merchant`](/merchant-review-feeds/xmlschema#\u003cmerchant\u003e) has\ndiffering create times across updates. As create time is an immutable field, changes to create\ntime will cause this issue to occur.\n| **Note:** this issue is referring to valid updates where update time changes. For more information regarding the data issue where create times changes, but update time doesn't change across updates, see [conflicting update](/merchant-review-feeds/data-issues/conflicting-update).\n\nHow to fix\n----------\n\nChoose one of the following options to resolve the issue:\n\n### Option A:\n\nIf you would like to use the original create time, re-deliver the [`review`](/merchant-review-feeds/xmlschema#\u003creview\u003e)\nor [`merchant`](/merchant-review-feeds/xmlschema#\u003cmerchant\u003e) with the\noriginal `create_timestamp` and updated `last_update_timestamp`.\n\n### Option B:\n\nIf you would like to use a new create time, re-deliver the\n[`review`](/merchant-review-feeds/xmlschema#\u003creview\u003e) or\n[`merchant`](/merchant-review-feeds/xmlschema#\u003cmerchant\u003e) with the new\n`create_timestamp` and updated `last_update_timestamp`. Then, inform the\nsupport team of the filename containing the entry. The support team can help with resolving this\nissue.\n\nExample\n-------\n\nOn March 1st, you upload the feed file \"2017_03_01.xml\" to your endpoint. The file contains an\nentry for a review that hasn't been sent previously: \n\n```scdoc\n\u003creview id=\"156368\" mid=\"2739\"\u003e\n \u003creviewer_name\u003eAda\u003c/reviewer_name\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 \u003ccountry_code\u003eUS\u003c/country_code\u003e\n \u003ctitle\u003eGreat prices\u003c/title\u003e\n \u003ccontent\u003eMy order arrived on time and I got a great price.\u003c/content\u003e\n \u003cratings\u003e\n \u003coverall min=\"1\" max=\"10\"\u003e9\u003c/overall\u003e\n \u003ccustomer_service min=\"1\" max=\"10\"\u003e10\u003c/customer_service\u003e\n \u003c/ratings\u003e\n \u003ccollection_method\u003eafter_fulfillment\u003c/collection_method\u003e\n\u003c/review\u003e\n```\n\nThe next day, you deliver the following feed file \"2017_03_02.xml\", which updates the create time\nfor review \"156368\": \n\n```scdoc\n\u003creview id=\"156368\" mid=\"2739\u003e\n \u003creviewer_name\u003eAda\u003c/reviewer_name\u003e\n \u003ccreate_timestamp\u003e2017-02-26T11:01:42Z\u003c/create_timestamp\u003e\n \u003clast_update_timestamp\u003e2017-02-26T11:01:42Z\u003c/last_update_timestamp\u003e\n \u003ccountry_code\u003eUS\u003c/country_code\u003e\n \u003ctitle\u003eGreat prices!\u003c/title\u003e\n \u003ccontent\u003eMy order arrived on time and I got a great price.\u003c/content\u003e\n \u003cratings\u003e\n \u003coverall min=\"1\" max=\"10\"\u003e9\u003c/overall\u003e\n \u003ccustomer_service min=\"1\" max=\"10\"\u003e10\u003c/customer_service\u003e\n \u003c/ratings\u003e\n \u003ccollection_method\u003eafter_fulfillment\u003c/collection_method\u003e\n\u003c/review\u003e\n```\n\nThe second entry for review \"156368\" creates a conflict in create time. You receive a\nnotification from the support team informing you that a data issue has occurred.\n\nAfter reviewing the documentation on how to fix this issue, you\nchoose [Option A](#option-a), to change the create time back to what it was originally.\nThe original create time was \"2017-02-25T03:02:23Z\", therefore, you deliver the following feed\nfile \"2017_03_10-fix.xml\", on March 10th: \n\n```scdoc\n\u003creview id=\"156368\" mid=\"2739\"\u003e\n \u003creviewer_name\u003eAda\u003c/reviewer_name\u003e\n \u003ccreate_timestamp\u003e2017-02-25T03:02:23Z\u003c/create_timestamp\u003e\n \u003clast_update_timestamp\u003e2017-03-09T02:40:23Z\u003c/last_update_timestamp\u003e\n \u003ccountry_code\u003eUS\u003c/country_code\u003e\n \u003ctitle\u003eGreat prices!\u003c/title\u003e\n \u003ccontent\u003eMy order arrived on time and I got a great price.\u003c/content\u003e\n \u003cratings\u003e\n \u003coverall min=\"1\" max=\"10\u003e9\u003c/overall\u003e\n \u003ccustomer_service min=\"1\" max=\"10\"\u003e10\u003c/customer_service\u003e\n \u003c/ratings\u003e\n \u003ccollection_method\u003eafter_fulfillment\u003c/collection_method\u003e\n\u003c/review\u003e\n```"]]
