nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Anyone Notice the SyncLog.dat File Is Now Larger Than It Used To Be?

markus1957

The cloud sync file SyncLog.dat associated with a data file used to grow to just over 5Mb and then a new SyncLog.dat file would get created; the old file renamed to SyncLog1.dat and the existing SyncLog1.dat file would be deleted.

Last month on May 29th I found the SyncLog.dat file had grown to almost 17Mb. The SyncLog1.dat file was just over 5Mb as is normal and dated April 10th. I renamed the large file and Quicken created a new SyncLog.dat file which I notice has now grown to almost 10Mb. I still have the April 10th SyncLog1.dat file. This is unexpected.

Is this a planned change in the software or is this limited to my file? In long ago times if the file got too large it would impact performance.

Find more posts tagged with

Windows

File

Accepted answers

All comments

Quicken Kristina

Hello @markus1957,

Thank you for letting us know this is happening. I checked the Sync log associated with my main file and observed that, while it is a little larger, the difference is approximately 20 KB, not 17 MB. I reached out internally to my team to see if there were any recent changes that might explain the behavior you observed, but I haven't received a response yet.

Are you observing this behavior with all of your Quicken files?

I look forward to your reply!

markus1957

I only have 1 file that might get this large as the others are temporary test files. Note the linked thread where a similar file size was observed. The dates when it may have begun are also similar.

https://community.quicken.com/discussion/7974439/cloud-sync-log-not-updating

jdparker225

@Quicken Kristina, It looks like @markus1957 and I are having the same problem. I didn't notice that Cloud Sync Log was continuing to grow until it reached 23MB when it stopped updating the log. If I had to guess, the problem was introduced in R67.10 maybe Build 27.1.67.10. Interestingly, May 29, 2026 is an important date in both our cases.

See

https://community.quicken.com/discussion/7974439/cloud-sync-log-not-updating

It seems like a useful workaround is to monitor the size of your Cloud Sync Log and, when it exceeds 5MB,

Close Quicken
Delete <QDF_file_name>_SyncLog1.dat
Rename <QDF_file_name>_SyncLog.dat to <QDF_file_name>_SyncLog1.dat
Reopen Quicken. This will cause the creation of a new <QDF_file_name>_SyncLog.dat.

I think this is a very important issue to get resolved ASAP. User problem reports submitted with log files may have Clould Sync Log with the data needed for problem analysis missing.

Thanks

Jim

Chris_QPW

Looking at mine, current_SyncLog.dat is 5MB and current_SyncLog1.dat is 8MB.

Looking at the data in each I see that both, they span about two months in time.

I suspect that they are trimmed by time, not size.

Note to look at *_SyncLog1.dat you would rename *_SyncLog.dat temporarily and the *_SyncLog1.dat to *_SyncLog.dat.

You read them by Help → Contact Support → Log Files → Cloud Sync Log.

If my assumption is correct, then how big they get will depend on both how frequently you use One Step Update and Sync to Mobile/Web and how many financial institutions/accounts you have in that two-month period.

jdparker225

@Chris_QPW, it is easier than that to look at *_SyncLog1.dat. Simply select the old one in the lower left corner of the Cloud Sync Log display. It defaults to “Current”, but you can change it.

Even if file switching is based on time rather than size, the issue is still very important because, it seems, that it stops recording if the file gets too big. My current Cloud Sync Log at 23MB had a little over a month’s activity in it. June 20 would have been the 2 month point and it did not switch. Later I’ll look at my old Cloud Sync Log, which is 5MB, to see its time frame. (I am currently not where I can access it. This is all based on memory.) Maybe they recently switched from size-based to time-based switching or something more complicated. There has been no big change in my activity or accounts in the last couple of years other than 3 FIs switching to EWC+; but that was months ago.

Thanks
Jim

jdparker225

@Chris_QPW, it is easier than that to look at *_SyncLog1.dat. Simply select the old one in the lower left corner of the Cloud Sync Log display. It defaults to “Current”, but you can change it.

Thanks
Jim

jdparker225

@Chris_QPW, I checked span of old Cloud Sync Log: April 4 to April 20, That's 17 days implying that, at that time, spinning off a new file was based on size (about 5MB). The last occurrence of "app-build:" in that log was "app-build: 27.1.66.28". So the change was introduced after app-build: 27.1.66.28. My new current Cloud Sync Log has "app-build: 27.1.67.10".

And why does my previous post appear twice?

Thanks

Jim

Chris_QPW

Thanks. As for why it posted twice, I have no idea. In someways I like the new format, but it seems to have a lot of unexpected quirks to it.

markus1957

The new SyncLog.dat file grew to over 10Mb, so I just opened it and saw that even though the byte count keeps growing, the readable log ended on June 7 or 8. It's probably corrupted as the last readable entry is dated June 7 but the entry before that is June 8.

Since not many are seeing this issue, I might try a complete uninstall and reinstall, including the hidden files. I've been bouncing back and forth between the beta and production so something may have got twisted in the install.

jdparker225

@markus1957, I wouldn't be so sure that others are not "having" the problem even though they may not be "seeing" it. I didn't notice it for almost a month after it stopped recording data. And that was just by chance that I noticed it at all. There were no outward appearances of anything being wrong. OSU was working fine. I had no trouble entering transactions or reconciling accounts.

Again, @Quicken Kristina, this is potentially a big issue. What is being done about it? I did report a problem with logs attached after 5/29 but before I noticed the problem. So the Cloud Sync Log for that submission won't be any good.

Thanks

Jim