This repository has been archived by the owner on Jun 2, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 746
SyncExpriedError: Last sync time is expired #858
Milestone
Comments
You'd better keep the sync interval less than 1 hour, keep a large interval doesn't make any sense. |
@glen-84 yep, |
fengmk2
added a commit
that referenced
this issue
Apr 4, 2016
@dead-horse See my discussion with @alsotang here (point 4). @fengmk2 Great, thank you. =) |
fengmk2
added a commit
that referenced
this issue
Apr 5, 2016
fengmk2
added a commit
that referenced
this issue
Apr 5, 2016
dead-horse
pushed a commit
that referenced
this issue
Apr 5, 2016
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
New installation of CNPM, with this sync config:
We get this e-mail every day:
lastSyncTime
is alwaysMon Mar 07 2016
(possibly the date of installation).Why isn't the
lastSyncTime
being updated? How do we fix this? Could it be time zone issues?Thanks.
PS. It should be
SyncExpiredError
and notSyncExpriedError
.Edit: Maybe on the first day, because the
syncInterval
is 24h, it actually tried to sync at just over 24h, which caused the error, and from that point on, it was always late? Maybe it should checksyncInterval
+ 10 mins or something?Edit 2: From the e-mails, it looks like the first sync was at
16:42:31
, and then it tries to sync at15:08:20
.The text was updated successfully, but these errors were encountered: