Articles on: Mobile App
This article is also available in:

How Synchronization Works

Articles on: Mobile App

Environment Synchronization
Refreshing the app

Environment Synchronization

After the login, the Periodic pull master data occurs loading all the components of the environment i.e. loads client information, user profile, teams, teammates, workflows, activity reports, list items and user insights/reports in that order.

This process involves fetching data from the server, ensuring that users always have the latest data.

The periodic pull master data starts automatically after the login or when you change a client. But you can also trigger it manually by pressing the refresh icon in your setting page.

We also have a process running in the background of the application that will play the logic every day.

Viewing mobile users last synchronization date is available on the Web app where you will be able to view the date which the user last synced his/her device.

For the app to function efficiently, the mobile user should allow the periodic pull to complete to 100%
In order to minimize the periodic pull master data, click on the X button at the top right corner of your screen.

For more information on the above actions, please watch this

Refreshing the app

Syncing/refreshing the application enables it to take effect of any changes that might have been done on the back end.

To refresh/sync the application, ensure you have active and good internet connection.

On the setting page, click on the refresh icon (Down arrow enclosed in a circle) at the top right of your screen.

Periodic push master data is the process that entails pushing your work to synchronize as soon as you complete an action on the mobile app when offline

For example:
If you are offline, a task will run in the background and the task will be notified/triggered to synchronize once you are back online

In the event that your synchronization fails you can see more details about it in the settings page schronisation and warnings section

In this section you will be able the see the reason why the pull couldn’t succeed. This will help us understand the cause of the error

You can also share the error with the support for an investigation. This will help us reproduce the error leading to a faster resolution.

For more information on the above actions, please watch this

Updated on: 26/04/2024

Was this article helpful?

Share your feedback


Thank you!