Strange behaviour regarding chronos

[Hendrik Brandes]

Hello,

we are using chronos as input for our timesheets. Mostly, the application is running well under chrome and firefox.

But: One of our collegues has the problem, that chronos said the values are stored, but they are not transferred to the underlying tryton-server.

So: He see his entries, but they are not stored in the backend.

All other employees are able to input their timesheet. Is it a problem, that we use the project-based approach of work-items: Projekt/SubProjekt/Task ?

Thank you and best regards,
Hendrik

[Cédric Krier]

On 2018-03-01 04:09, 'Hendrik Brandes' via tryton wrote:
> we are using chronos as input for our timesheets. Mostly, the application is running well under chrome and firefox.
>
> But: One of our collegues has the problem, that chronos said the values are stored, but they are not transferred to the underlying tryton-server.
>
> So: He see his entries, but they are not stored in the backend.

The synchronisation to the server is asynchronous so it can work
offline.
The synchronisation starts every minutes and it tests if the browser is
not offline. So maybe for some reason: navigator.offline is true.
Otherwise you should check (using debug feature of addons) if the
requests are correctly sent to the server.

--
Cédric Krier - B2CK SPRL
Email/Jabber: cedric...@b2ck.com
Tel: +32 472 54 46 59
Website: http://www.b2ck.com/

[Hendrik Brandes]

Am Donnerstag, 1. März 2018 14:00:09 UTC+1 schrieb Cédric Krier:
> On 2018-03-01 04:09, 'Hendrik Brandes' via tryton wrote:
> > we are using chronos as input for our timesheets. Mostly, the application is running well under chrome and firefox.
> >
> > But: One of our collegues has the problem, that chronos said the values are stored, but they are not transferred to the underlying tryton-server.
> >
> > So: He see his entries, but they are not stored in the backend.
>
> The synchronisation to the server is asynchronous so it can work
> offline.
> The synchronisation starts every minutes and it tests if the browser is
> not offline. So maybe for some reason: navigator.offline is true.
> Otherwise you should check (using debug feature of addons) if the
> requests are correctly sent to the server.

Thank you for this hint with "offline". After checking the status, we found out, that there was a proxy-configuration within this browser and this proxy do not accept the tryton-server.

After removing the proxy, it works as expected. But the existing entries had not been transferred. We must save each entry manual.

[Cédric Krier]

On 2018-03-01 05:43, 'Hendrik Brandes' via tryton wrote:
> After removing the proxy, it works as expected. But the existing
> entries had not been transferred. We must save each entry manual.

Normally, it should synchronise but it can take times because we use
chrome.alarms with delayInMinutes=1 and periodInMinutes=5. But this is
not guarantee as the browser may decide to delay the fire.

If you create the entry manually, you risk to have duplicates.

[Hendrik Brandes]

Am Donnerstag, 1. März 2018 15:10:08 UTC+1 schrieb Cédric Krier:
> On 2018-03-01 05:43, 'Hendrik Brandes' via tryton wrote:
> > After removing the proxy, it works as expected. But the existing
> > entries had not been transferred. We must save each entry manual.
>
> Normally, it should synchronise but it can take times because we use
> chrome.alarms with delayInMinutes=1 and periodInMinutes=5. But this is
> not guarantee as the browser may decide to delay the fire.
>
> If you create the entry manually, you risk to have duplicates.

Ok. Thank you, we will observe this case.