# finisher: file modified but not rescanned; will try again later

**URL:** https://forum.syncthing.net/t/finisher-file-modified-but-not-rescanned-will-try-again-later/10916
**Category:** Support
**Created:** [November 3, 2017, 1:58pm UTC](https://forum.syncthing.net/t/finisher-file-modified-but-not-rescanned-will-try-again-later/10916 "2017-11-03T13:58:05Z")
**Posts on this page:** 10
**Page:** 1

<div class="post-metadata">

### Author: ![koppor](https://forum.syncthing.net/user_avatar/forum.syncthing.net/koppor/32/4201_2.png) [@koppor](https://forum.syncthing.net/u/koppor)
#### Post date: [November 3, 2017, 1:58pm UTC](https://forum.syncthing.net/t/finisher-file-modified-but-not-rescanned-will-try-again-later/10916/1 "2017-11-03T13:58:05Z")

</div>

Coming from [Symlinks as folder root broken on Windows · Issue #4353 · syncthing/syncthing · GitHub](https://github.com/syncthing/syncthing/issues/4353#issuecomment-341660539), I installed v0.14.40-rc.4.

I removed my synced folder and added it again. I constantly get following output:

> finisher: file modified but not rescanned; will try again later

However, the file named is not modified on either side.

---

<div class="post-metadata">

### Author: ![koppor](https://forum.syncthing.net/user_avatar/forum.syncthing.net/koppor/32/4201_2.png) [@koppor](https://forum.syncthing.net/u/koppor)
#### Post date: [November 3, 2017, 2:35pm UTC](https://forum.syncthing.net/t/finisher-file-modified-but-not-rescanned-will-try-again-later/10916/2 "2017-11-03T14:35:21Z")

</div>

Renaming the file on the sending side solved the issue for me.

---

<div class="post-metadata">

### Author: ![AudriusButkevicius](https://forum.syncthing.net/user_avatar/forum.syncthing.net/audriusbutkevicius/32/277_2.png) [@AudriusButkevicius](https://forum.syncthing.net/u/AudriusButkevicius)
#### Post date: [November 3, 2017, 3:40pm UTC](https://forum.syncthing.net/t/finisher-file-modified-but-not-rescanned-will-try-again-later/10916/3 "2017-11-03T15:40:59Z")

</div>

If the case of the foldee changed, this could happen.

---

<div class="post-metadata">

### Author: ![spo0okie](https://forum.syncthing.net/letter_avatar_proxy/v4/letter/s/b5ac83/32.png) [@spo0okie](https://forum.syncthing.net/u/spo0okie)
#### Post date: [November 14, 2017, 4:57am UTC](https://forum.syncthing.net/t/finisher-file-modified-but-not-rescanned-will-try-again-later/10916/4 "2017-11-14T04:57:22Z")

</div>

i have the same problem. Is new version fix this?

---

<div class="post-metadata">

### Author: ![lee3521](https://forum.syncthing.net/letter_avatar_proxy/v4/letter/l/8dc957/32.png) [@lee3521](https://forum.syncthing.net/u/lee3521)
#### Post date: [November 19, 2017, 2:02am UTC](https://forum.syncthing.net/t/finisher-file-modified-but-not-rescanned-will-try-again-later/10916/5 "2017-11-19T02:02:22Z")

</div>

Same problem here as well. Unfortunately I have over 692 files in one directory that have the error message, so renaming that many files is not an option for me. The strange thing is that I have three other Syncthing servers that are synchronized with the same folder and those three servers are all showing up to date.

---

<div class="post-metadata">

### Author: ![AudriusButkevicius](https://forum.syncthing.net/user_avatar/forum.syncthing.net/audriusbutkevicius/32/277_2.png) [@AudriusButkevicius](https://forum.syncthing.net/u/AudriusButkevicius)
#### Post date: [November 19, 2017, 2:15am UTC](https://forum.syncthing.net/t/finisher-file-modified-but-not-rescanned-will-try-again-later/10916/6 "2017-11-19T02:15:20Z")

</div>

You can try renaming the directory.

---

<div class="post-metadata">

### Author: ![lee3521](https://forum.syncthing.net/letter_avatar_proxy/v4/letter/l/8dc957/32.png) [@lee3521](https://forum.syncthing.net/u/lee3521)
#### Post date: [November 19, 2017, 2:18am UTC](https://forum.syncthing.net/t/finisher-file-modified-but-not-rescanned-will-try-again-later/10916/7 "2017-11-19T02:18:03Z")

</div>

Thanks I had not thought of that. Would I also need to change the shared folder path to match the new name?

---

<div class="post-metadata">

### Author: ![AudriusButkevicius](https://forum.syncthing.net/user_avatar/forum.syncthing.net/audriusbutkevicius/32/277_2.png) [@AudriusButkevicius](https://forum.syncthing.net/u/AudriusButkevicius)
#### Post date: [November 19, 2017, 2:21am UTC](https://forum.syncthing.net/t/finisher-file-modified-but-not-rescanned-will-try-again-later/10916/8 "2017-11-19T02:21:19Z")

</div>

Not sure I understand. If all the files within some subdirectory in a folder, then you can rename the subdirectory. If they are at the root of the folder, or scattered, you might want to upgrade to the latest rc which should have this bug fixed.

---

<div class="post-metadata">

### Author: ![lee3521](https://forum.syncthing.net/letter_avatar_proxy/v4/letter/l/8dc957/32.png) [@lee3521](https://forum.syncthing.net/u/lee3521)
#### Post date: [November 19, 2017, 2:57am UTC](https://forum.syncthing.net/t/finisher-file-modified-but-not-rescanned-will-try-again-later/10916/9 "2017-11-19T02:57:13Z")

</div>

I am sharing the root folder which is named HBT Service, however, the problem files are in multiple folders which are sub folders inside the HBT Service folder. There are 109,208 files and 15,175 folders inside the HBT Service folder. I am using SyncTrayzor and do not see an option to install the RC versions. I may have to just wait until the 28th when the RC is officially released. These are production machines with 3.7 million files being synchronized, and the root synchronized folders are mapped to about 100 employees. I am afraid to experiment too much.

---

<div class="post-metadata">

### Author: ![system](https://forum-uploads.syncthingcdn.net/original/2X/0/0b50e0a202b22ae6a67190759e8c868805b8ed9f.png) [@system](https://forum.syncthing.net/u/system)
#### Post date: [December 19, 2017, 3:09am UTC](https://forum.syncthing.net/t/finisher-file-modified-but-not-rescanned-will-try-again-later/10916/10 "2017-12-19T03:09:00Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
