Hi Mesh,

When the initialization starts can you go to Explore Mobile User → Select your user → Check the status of your device?

Does it say “Init waiting for GP” or “Init waiting for MWS”? If it says “Init waiting for GP”, then it could be an issue with a large amount of data for Grouped Push entities. If it works after 12 hours that could very well be the case.

If that is the case you may need to apply some permission set filters to those entities to reduce the data volume so that the initialization time can be reduced.

Thanks and Best Regards,
Ibrahim

Hi Ibrahim,

Many thanks for your contribution. is currently in active state now as shown in screenshot below 

Hi Mesh,

You can check the time spent to sync on each entity by Synchronized entities tab in Mobile user details window. If you can noticed there's exceptional time for some entities, you can set up permission set filters to restrict unwanted data sent to mobile user.

Hi Mesh,

That status is the user status not the device status. Please see below screenshot:

Please check this status when the user is trying to initialize his device. If this status is “Waiting for GP” then it could be a performance delay with Grouped Push. If not it could be a performance issue with other entities.

If its not an issue with Grouped Push (status not in “Waiting for GP”) then you should attempt@Dakshinie Wickramasinghe’s test above.

Best Regards,
Ibrahim

There is also a Mobile Status lobby page that shows data volumes and sync times. It might be useful in finding out the performance problem here

thanks everyone for your contribution. 

@James Ashmore, please can you share a screenshot on the Mobile status lobby page for clarify? 

@Ibrahim Naazir in scenarios where is “Init waiting for MWS”? what do we do? 

@meshfemi there are a few things you can check. First check Grouped Push Transaction Traces window to see if there are any errors. I dont think there are any errors as it works after some hours.

If there are no errors it could very well be a performance issue. Can you check the number of records per GP entity using the below query:

SELECT app_name, app_version, entity, transaction_filter_id, COUNT(*)
FROM mobile_transaction_offline_tab
GROUP BY app_name, app_version, entity, transaction_filter_id
ORDER BY COUNT(*) DESC

This should sort it by the largest number of records. If you can perhaps send us a screenshot of the results maybe we can find a better clue.

Best Regards,
Ibrahim

Here you go

You need to ensure the Schedule Task “Touch Apps Daily Statistics” is running to capture this data

Cheers

James

For those getting there status of “Init waiting for GP”, what I have done is disconnect the users device from their client.  Then in APPS I disable and delete their device.  Then I have them reconnect and it goes through with no issue.  If it’s a performance issue shouldn’t it happen every time?  I am seeing this with some users using mWO Service 10 (ServiceEngApp 1.6).  

Hi,

Similar issue in thread mWO initialization time - identify slowness | IFS Community

Best regards,

Hubert

This slowness should only be seen the first time a user connects with MWO with a data set not already prepared by the Grouped Push process.

After the Grouped Push process has collected the data the subsequent time the user (or different user allocated to the same data set) connects then the data is already prepared and no time delay will be seen in the Grouped Push process.