Sitecore does not automatically do anything with serialization files from TDS out of the box.

Now this doesn't rule out a custom schedule task that someone may have put into the system, but that doesn't seem likely.

When TDS syncs, it can be configured to publish any items that it syncs, but that would be dependent upon how you have TDS setup in your CI deploymemt process.

Most likely what happened, is that TDS synced the home item in the master database only.

Then one of the following happened:

1. Someone published the home item, sending the changes from the TDS sync to the web database, and cleared CD content caching.
2. TDS did publish the item to the web database, but the CD item caching didn't clear until a later time: either by a worker process reset or another publish later on triggered cache clearing correctly.

Either way, the answer is Sitecore doesn't do anything to serialized files automatically, unless someone customized Sitecore to do so, which would require further invesitgation.

###Troubleshooting

It might be worth while to look at your Sitecore log and look for the Publish item messages and see if someone published it around the time you saw it change.

Additionally, generally there is a log file entry when TDS updates an item. Do a search for the Home path in your log and see if that produces clues.

Also look at your CD logs and see if there was a recycle around the time you saw the change.

Sitecore does not automatically do anything with serialization files from TDS out of the box.

Now this doesn't rule out a custom schedule task that someone may have put into the system, but that doesn't seem likely.

When TDS syncs, it can be configured to publish any items that it syncs, but that would be dependent upon how you have TDS setup in your CI deploymemt process.

Most likely what happened, is that TDS synced the home item in the master database only.

Then one of the following happened:

1. Someone published the home item, sending the changes from the TDS sync to the web database, and cleared CD content caching.
2. TDS did publish the item to the web database, but the CD item caching didn't clear until a later time: either by a worker process reset or another publish later on triggered cache clearing correctly.

Either way, the answer is Sitecore doesn't do anything to serialized files automatically, unless someone customized Sitecore to do so, which would require further invesitgation.

Troubleshooting

It might be worth while to look at your Sitecore log and look for the Publish item messages and see if someone published it around the time you saw it change.

Additionally, generally there is a log file entry when TDS updates an item. Do a search for the Home path in your log and see if that produces clues.

Also look at your CD logs and see if there was a recycle around the time you saw the change.

Sitecore does not automatically do anything with serialization files from TDS out of the box.

Now this doesn't rule out a custom schedule task that someone may have put into the system, but that doesn't seem likely.

When TDS syncs, it can be configured to publish any items that it syncs, but that would be dependent upon how you have TDS setup in your CI deploymemt process.

Most likely what happened, is that TDS synced the home item in the master database only.

Then one of the following happened:

1. Someone published the home item, sending the changes from the TDS sync to the web database, and cleared CD content caching.
2. TDS did publish the item to the web database, but the CD item caching didn't clear until a later time: either by a worker process reset or another publish later on triggered cache clearing correctly.

Either way, the answer is Sitecore doesn't do anything to serialized files automatically, unless someone customized Sitecore to do so, which would require further invesitgation.

Sitecore does not automatically do anything with serialization files from TDS out of the box.

Now this doesn't rule out a custom schedule task that someone may have put into the system, but that doesn't seem likely.

When TDS syncs, it can be configured to publish any items that it syncs, but that would be dependent upon how you have TDS setup in your CI deploymemt process.

Most likely what happened, is that TDS synced the home item in the master database only.

Then one of the following happened:

1. Someone published the home item, sending the changes from the TDS sync to the web database, and cleared CD content caching.
2. TDS did publish the item to the web database, but the CD item caching didn't clear until a later time: either by a worker process reset or another publish later on triggered cache clearing correctly.

Either way, the answer is Sitecore doesn't do anything to serialized files automatically, unless someone customized Sitecore to do so, which would require further invesitgation.

###Troubleshooting

It might be worth while to look at your Sitecore log and look for the Publish item messages and see if someone published it around the time you saw it change.

Additionally, generally there is a log file entry when TDS updates an item. Do a search for the Home path in your log and see if that produces clues.

Also look at your CD logs and see if there was a recycle around the time you saw the change.