Navigation

    Kopano
    • Register
    • Login
    • Search
    • Categories
    • Get Official Kopano Support
    • Recent
    Statement regarding the closure of the Kopano community forum and the end of the community edition

    Outlook resends calender entries while first sync is in process

    Z-Push when using other backends
    1
    1
    296
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • sjo
      sjo last edited by

      Hi,
      we use z-push with a self developed backend to sync appointments,
      contacts and tasks with our enterprise software.

      Recently we had some cases where customers reported a duplication
      of calender entries when using outlook as client.

      At least in one case the customer was copying many calender entries from another
      Outlook calender to the z-push synced calender to “import” the entries
      to our system.

      While analysing the logs we found that obviously Outlook starts
      to sync (sends calender entries to z-push) and while this block
      of entries (about 120 entries in this case) is processed by z-push and our backend
      Outlook starts to resend the same entries again. In this case even a third sync
      was sent by Outlook while the second was processed.

      Our suspicion is Outlook starts the sync, waits for a certain
      amount of time and if it gets no response in time (this seems to be about 1 minute)
      it simply repeats the sync. So it seems our processing needs to much time
      for the impatient Outlook, at least with many entries to sync.

      Has anybody else experienced this? And is there a simple solution
      (a z-push configuration / Outlook setting etc.) for this?

      Is SYNC_MAX_ITEMS only working in one direction (client requests
      changes from the server)? If we could reduce the amount of entries
      send in one block by Outlook the time to process this “block”
      could be reduced so the “timeout” would not get triggered (no perfect
      solution but it would at least help to avoid this).

      Otherwise the only solution which comes to mind is that we
      have to check the uuid send from outlook and
      reject (rather ignore) all new entries whith already known uuids.

      Any suggestions welcome.

      Regards,
      Stephan

      1 Reply Last reply Reply Quote 0
      • First post
        Last post