Auto-update. A check on how it works

Hi

I just want to check how the auto-update setting works.

I have it set to ‘Daily’. If I make more than one new version in a day (eg
I start the day at version 212 and end at 215), what happens when the user
using 211 submits a form at the end of the day? Do they get version 212 (ie
the the one up from the one they’ve got) or do they jump straight to
version 215 (the latest version available).

The reason I am asking is that I went from version 1210 to 1214 yesterday
and since then five workers have submitted but only one has 1214. See
screenshot attached.

Thanks

Simon

Google ChromeScreenSnapz020.pdf (40.2 KB)

Hi Simon,

Two different questions here:

First one:
“Daily” updates don’t quite have that specific of a schedule (end of day).

A “Daily” update is triggered the first time a user logs in on a calendar
day. If the phone can’t contact the server at all it continues to try again
on subsequent logins and intermittently.

Second one:
When a user in a project space looks for an Update, they always get the
very newest starred build, regardless of their current version. However, if
the update is taking a long time to come down to the phone for some reason
(IE: A phone has started an update, and is incrementally downloading
pieces of it as internet is available), the phone will continue attempting
to complete that update for a fixed window (a few days) before deciding
that it should start over and again request the very newest version from
the server.

This is done so that the phone will be able to take advantage of a
"trickle" of data without it constantly being reset, but won’t get "stuck"
on a specific update (one case where this could come up would be if a user
accidentally included a multimedia file that was prohibitively large, and
the phone could never manage to finish downloading it).

-Clayton

··· On Thu, Jan 12, 2017 at 11:09 AM, Simon Berry wrote:

Hi

I just want to check how the auto-update setting works.

I have it set to ‘Daily’. If I make more than one new version in a day (eg
I start the day at version 212 and end at 215), what happens when the user
using 211 submits a form at the end of the day? Do they get version 212 (ie
the the one up from the one they’ve got) or do they jump straight to
version 215 (the latest version available).

The reason I am asking is that I went from version 1210 to 1214 yesterday
and since then five workers have submitted but only one has 1214. See
screenshot attached.

Thanks

Simon


You received this message because you are subscribed to the Google Groups
"commcare-users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to commcare-users+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Hi Clayton

Thank you for this very full explanation.

Regards

Simon
13/1/17

··· On Thursday, January 12, 2017 at 7:59:11 PM UTC, Clayton Sims wrote: > > Hi Simon, > > Two different questions here: > > First one: > "Daily" updates don't quite have that specific of a schedule (end of day). > > A "Daily" update is triggered the first time a user logs in on a calendar > day. If the phone can't contact the server at all it continues to try again > on subsequent logins and intermittently. > > Second one: > When a user in a project space looks for an Update, they always get the > very newest starred build, regardless of their current version. However, if > the update is taking a long time to come down to the phone for some reason > (IE: A phone has *started* an update, and is incrementally downloading > pieces of it as internet is available), the phone will continue attempting > to complete that update for a fixed window (a few days) before deciding > that it should start over and again request the very newest version from > the server. > > This is done so that the phone will be able to take advantage of a > "trickle" of data without it constantly being reset, but won't get "stuck" > on a specific update (one case where this could come up would be if a user > accidentally included a multimedia file that was prohibitively large, and > the phone could never manage to finish downloading it). > > -Clayton > > On Thu, Jan 12, 2017 at 11:09 AM, Simon Berry <si...@colalife.org > wrote: > >> Hi >> >> I just want to check how the auto-update setting works. >> >> I have it set to 'Daily'. If I make more than one new version in a day >> (eg I start the day at version 212 and end at 215), what happens when the >> user using 211 submits a form at the end of the day? Do they get version >> 212 (ie the the one up from the one they've got) or do they jump straight >> to version 215 (the latest version available). >> >> The reason I am asking is that I went from version 1210 to 1214 yesterday >> and since then five workers have submitted but only one has 1214. See >> screenshot attached. >> >> Thanks >> >> Simon >> >> -- >> You received this message because you are subscribed to the Google Groups >> "commcare-users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to commcare-user...@googlegroups.com . >> For more options, visit https://groups.google.com/d/optout. >> > >

Of course! Anything I can do to help.

-Clayton

··· On Fri, Jan 13, 2017 at 4:44 AM, Simon Berry wrote:

Hi Clayton

Thank you for this very full explanation.

Regards

Simon
13/1/17

On Thursday, January 12, 2017 at 7:59:11 PM UTC, Clayton Sims wrote:

Hi Simon,

Two different questions here:

First one:
“Daily” updates don’t quite have that specific of a schedule (end of day).

A “Daily” update is triggered the first time a user logs in on a calendar
day. If the phone can’t contact the server at all it continues to try again
on subsequent logins and intermittently.

Second one:
When a user in a project space looks for an Update, they always get the
very newest starred build, regardless of their current version. However, if
the update is taking a long time to come down to the phone for some reason
(IE: A phone has started an update, and is incrementally downloading
pieces of it as internet is available), the phone will continue attempting
to complete that update for a fixed window (a few days) before deciding
that it should start over and again request the very newest version from
the server.

This is done so that the phone will be able to take advantage of a
"trickle" of data without it constantly being reset, but won’t get "stuck"
on a specific update (one case where this could come up would be if a user
accidentally included a multimedia file that was prohibitively large, and
the phone could never manage to finish downloading it).

-Clayton

On Thu, Jan 12, 2017 at 11:09 AM, Simon Berry si...@colalife.org wrote:

Hi

I just want to check how the auto-update setting works.

I have it set to ‘Daily’. If I make more than one new version in a day
(eg I start the day at version 212 and end at 215), what happens when the
user using 211 submits a form at the end of the day? Do they get version
212 (ie the the one up from the one they’ve got) or do they jump straight
to version 215 (the latest version available).

The reason I am asking is that I went from version 1210 to 1214
yesterday and since then five workers have submitted but only one has 1214.
See screenshot attached.

Thanks

Simon


You received this message because you are subscribed to the Google
Groups “commcare-users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to commcare-user...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


You received this message because you are subscribed to the Google Groups
"commcare-users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to commcare-users+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.