When was Device Maintenance last run on the S21?  it is amazing how many little issues go away once that has been done.   Might not clear the old duplicates, but may stop new ones for a good while.

When the GMS logfile (mobility-agent.log) is in DEBUG level you can see if the GMS server is sending it once or twice, if once then the device itself for some reason shows it more then once. GMS does not have influence on what the device does with the data after it got it

Sorry still in debugging the issue. Today i switched the user to a standalone gms.

As far as i can see until yet is that the new testing appointment only transferrred once in mobility-agent and groupwise-agent.

Will look at that for some days and report.

Martin -  we do have an open defect on this issue that engineering hasn't fixed yet.  Depending on the work needed to fix it, we may or may not have an FTF for the 18.4.2 branch and it will be in 18.5.  It could even miss that release, again depending on what the issue is.  We will know more once they start work on the defect. - Pam

Hi,

got more information now on the issue.

In the logfiles i see that each time the event where doubled or now three times the appointment was send oncce again.

Did send a new appointment called 'Einsatzbesprechung Voyager' (took something which wouldn't be accidentally twice in the whole calendar). The user ist the only user on the gms. user was first connected on 20230116 before sending the appointment.

root@cancer:/var/log/datasync/connectors# zgrep Voyager mobility-agent.log-20230*
mobility-agent.log-20230117.gz:    <subject>Thomas Christen accepted Einsatzbesprechung Voyager; (23 Aug 2023 15:30 pm)  Mitteleurop&#228;ische Sommerzeit</subject>
mobility-agent.log-20230117.gz:    <subject>Einsatzbesprechung Voyager</subject>
mobility-agent.log-20230117.gz:    <subject>Einsatzbesprechung Voyager</subject>
mobility-agent.log-20230117.gz:apptDebugInfo: subject = Einsatzbesprechung Voyager, objId = 1216707933432333212, userId = christen.gwdle.gwmta1, devId = 22b958b895a711edac1800505697761b, type = SamsungDevice, action = appt sync, tempAppt = False, startTime = 2023-08-23T13:30:00Z
mobility-agent.log-20230118.gz:apptDebugInfo: subject = Einsatzbesprechung Voyager, objId = 1216707933432333212, userId = christen.gwdle.gwmta1, devId = 22b958b895a711edac1800505697761b, type = SamsungDevice, action = appt sync, tempAppt = False, startTime = 2023-08-23T13:30:00Z
mobility-agent.log-20230126.gz:apptDebugInfo: subject = Einsatzbesprechung Voyager, objId = 1216707933432333212, userId = christen.gwdle.gwmta1, devId = 22b958b895a711edac1800505697761b, type = SamsungDevice, action = appt sync, tempAppt = False, startTime = 2023-08-23T13:30:00Z

On 20230117 the appointments show twice. Since yesterday the appointments are three times on the phone.

Next step activating debug.

Martin - engineering think they have a fix for it.  I have sent it to one customer for testing.  If you would also like this to see if it fixes your issue, please open a new case and ask for the temporary fix from defect 619126.  - Thanks Pam

Thanks, i will check that.