There are multiple reasons why you might experience a delay in events showing on your mobile app diary. Some examples are detailed below;
- If many apps are open on the device used, there may not be enough processing power for the Commusoft app to access. Closing the Commusoft app along with any unnecessary apps will clear the device cache, freeing up memory and processing power the app needs to function. When you open the Commusoft app it then has access to more device resources.
We recommend any device used to run the Commusoft app exceeds the minimum device requirements. The Commusoft app will function on a device that meets the minimum requirements but will perform better with more device resources available.
- Low signal or bad connection at the time the event is added. The best way to test your connection is to visit a website and try to load a video, eg. BBC News or Youtube.
Any newly created data will be added to the queue to sync and wait for a better connection to begin the sync. This includes updated events on the mobile or changes/additions on the web.
- There is a large amount of data waiting to sync between the server and the device. If there is a large amount of activity on the web, this data will queue to sync to mobile devices. Any diary event added during this time would be added behind all the previously created data and try to wait for this to sync first.
This can also come into play when several devices are used by the same user. For example, if they have a phone and tablet, and use their phone the majority of the time, the tablet will have a larger queue of data when it is next used. The user will need to allow time for the queue of data to pass to the tablet in order to have the most up-to-date information.
- The user is not following recommended practices for mobile app usage. These steps ensure that the Commusoft app and device used are operating well and reduce the likelihood of this type of issue occurring. The usage requirements are;
- Close the app daily. Leaving the app open in the background for prolonged time periods can cause further issues and a backlog of queued data to sync. Closing any open app when not in use will ensure the device has enough memory free at any given time.
- Accept events when the user is notified, the night before or morning of the event. Web users will see at a glance that all events have been seen and the engineer can attend, giving you time to advise the engineer to manually sync the app in cases where the event did not sync.
N.B. - Multiple events can be accepted at any given time and events can be edited if accepted.
- Keep the app up to date. App stores allow automatic updates for installed apps which can ensure you receive the latest version as they are released.
- Reinstall the app once every 3 months so you have a fresh database downloaded regularly.
N.B. - Always ensure the app and web have synced before uninstalling the app.
- Apps are intended for daily usage. If the app is not used daily there will be a larger backlog of data to sync when it is opened. Uninstall the app when not actively in use, eg. during annual leave/holiday periods over 5 days.
If you do not see a thumbs up on the web, the event may not be showing for the engineer. This is especially important for same-day edits/additions to the diary and office staff will need to check the diary to ensure events are accepted.
📘️Minimum requirements for running Commusoft
📘️Mobile Apps - Diary event statuses
📘️Diary event statuses and icons