# Create time changed

## Description

A create time changed issue occurs when a [`review`](https://developers.google.com/merchant-review-feeds/xmlschema#<review>)
or [`merchant`](https://developers.google.com/merchant-review-feeds/xmlschema#<merchant>) has
differing create times across updates. As create time is an immutable field, changes to create
time will cause this issue to occur.

> [!NOTE]
> **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](https://developers.google.com/merchant-review-feeds/data-issues/conflicting-update).

## How to fix

Choose one of the following options to resolve the issue:

### Option A:

If you would like to use the original create time, re-deliver the [`review`](https://developers.google.com/merchant-review-feeds/xmlschema#<review>)
or [`merchant`](https://developers.google.com/merchant-review-feeds/xmlschema#<merchant>) with the
original `create_timestamp` and updated `last_update_timestamp`.

### Option B:

If you would like to use a new create time, re-deliver the
[`review`](https://developers.google.com/merchant-review-feeds/xmlschema#<review>) or
[`merchant`](https://developers.google.com/merchant-review-feeds/xmlschema#<merchant>) with the new
`create_timestamp` and updated `last_update_timestamp`. Then, inform the
support team of the filename containing the entry. The support team can help with resolving this
issue.

## Example

On March 1st, you upload the feed file "2017_03_01.xml" to your endpoint. The file contains an
entry for a review that hasn't been sent previously:

```
<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>
```

The next day, you deliver the following feed file "2017_03_02.xml", which updates the create time
for review "156368":

```
<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>
```

The second entry for review "156368" creates a conflict in create time. You receive a
notification from the support team informing you that a data issue has occurred.

After reviewing the documentation on how to fix this issue, you
choose [Option A](https://developers.google.com/merchant-review-feeds/data-issues/create-time-changed#option-a), to change the create time back to what it was originally.
The original create time was "2017-02-25T03:02:23Z", therefore, you deliver the following feed
file "2017_03_10-fix.xml", on March 10th:

```
<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>
```