If the activity timeline has stopped updating, the usual causes are the cloud being unreachable, a heavy first scan still running, or simply no checks being due yet.
Understand the rhythm
SyncNow observes on an interval, not continuously, and it only records changes. So a quiet timeline often just means nothing on the server has changed since the last check.
What to check
- Open the project card and read its status and last-observed time. A recent time means it is working.
- A first-time project runs a full bootstrap scan that can take a while on large sites. Let it finish.
- Confirm the cloud is reachable. SyncNow coordinates through it, so a network hiccup pauses observation until it recovers.
- If the FTP server is slow or refusing connections, SyncNow waits and retries rather than hammering it.
Recovery
After repeated failures SyncNow enters a read-only safe mode and recovers on its own once cycles run clean. You can also restart SyncNow to force a fresh cycle. If it stays stuck, the diagnostics logs show the exact step failing.
SyncNow