Hi @didous,

Update 5 brought in background sync via the push notifications. If this is setup then the mobile device does not need to always be active and in the foreground of the device for the sync to occur, it will instead sync in the background to help work through the data that is queued.

If the push notification and background sync is not in place then the app does need to be active and in the foreground for any sync to take place.

If the queued message that is waiting is in that state due to a temporary connection issue it should retry when it next connects. There have been issue though where large transactions have been waiting indefinitely due to middleware taking on the transaction and closing the transaction due to time out preventing the response from coming through. In that case the queue will not clear until the source of the response failure is corrected.

Kind regards,

Lee Pinchbeck

Hi @didous ,

• Yes, the sync cycle only runs when the app is in the foreground, unless Push Messaging has been enabled and configured to send silent push messages to trigger background sync. 

  The MOBILE SILENT PUSH Scheduled Process needs to be activated for background sync to function on a timed basis.

  RnD have released a mobile messagingguide document with Update 10. I have attached the document here for further reference.

• If the messages are stacked in the sync queue due to a system performance issue such as connection issues, the messages will sync to the server when the connection is restored. No initialization is required unless you need to process all sync rules and generate a new mobile database for your device. But if there are delays in the acknowledgement send from the server due to the performance of the server, the messages will not get synced until the acknowledgement is received .

Best Regards