To sketch the problem, let us change a business partner. But this applies to any object we send with NAV.
1. Suppose our push is set to every 3 minutes, and Job Queue Entry ends at 10:15 (Coresystems server 10:13, 120 seconds time difference between servers).
Based on the latest DateTime stamp of the Job Queue Log Entry NAV requests the changed business partners changed since 10:12 (converted to Unix Time is 1501056720000).
As no changes have been made at 10:13, nothing is returned from the Coresuite server.
2. Today at 10:14 a user changes a business partner through the Coresuite app.
Converted to Unix Time on the Coresuite server, the lastChanged field is filled with '1501056840000'.
3. The next time NAV performs a Get through the Job Queue Entry is at 10:18 (in reality at 10:16 by 120 seconds time difference between the servers).
Based on the latest DateTime stamp of the Job Queue Log Entry NAV requests the changed business partners changed since 10:15 (converted to Unix Time is 1501056900000).
Since 1501056840000 <1501056900000, nothing is returned here.
As a result, you have timegaps of 120 seconds each that are not concealed.
So when we are dealing with a server time difference, we noticed that the bigger the interval the more data is not retreived. So to know the exact date/time of the Coresystems server would help a lot in solving this problem.
Maybe you can provide a API that we can ask the actual server date/time?