Manual Conflict w/ Automatic on..?

[Mark Stuller]

We received the below but have auto-resolution turned on for this configuration. Ideas?

Thanks, Mark

Nov 09, 2016 8:19:16 AM com.prosc.mirror.config.server.SyncServer$3 call
SEVERE: Sync between filemaker8.oda.state.or.us / BeFoodSafe5 (FileMaker Server) and swong iPad BeFoodSafe( username 'developer', running Go_iPad 15.0.2 on 76.115.11.132, ping time: 471 ms, machine name: 'swong' )
Last sync failed: com.prosc.sync.AbortException: Complete manual conflict resolution, then sync again

[Mark Stuller]

FWIW

We performed a force-quit of FileMakerGo and the client was able to sync successfully!?!

Mark

 

[Jesse Barnum]

When you say auto-resolution, are you talking about field merging, or do you mean that you have the conflict resolution strategy set to 'most recent wins'?

[Mark Stuller]

Hi Jesse

We have "conflict resolution strategy set to 'most recent wins'"

Mark

[Jesse Barnum]

OK, if it happens again, please submit a problem report and I'll check into the log file for it.

[Mark Stuller]

I was thinking this is a client issue as a force-quit of Go and subsequent sync completed successfully...