If synchronization occurs after a notification, or if a notification arrives but data is not updated, both symptoms require you to evaluate the subscription settings.
Most importantly, evaluate how the cache group interval, sync group interval, and notification threshold properties are configured. If one of these items is mistimed, the user is likely to experience an unlikely result.
- Check the settings of the cache group used by the package.
- In Sybase Control Center, expand the Packages node, select the package name, then choose the Cache Group tab.
- Select the box beside the cache group name and click Properties.
- Verify:
- The cache interval or schedule used to refresh data in the Unwired Server cache based on changes in the back-end EIS data source. Make note of that refresh interval to use in the next step.
- Select the Subscriptions tab and verify:
- That the user subscription has not been removed or suspended.
- That push synchronization is used as required. Follow up with the user to ensure that push synchronization is enabled on the device.
- That the synchronization group interval is configured appropriately based on the cache interval or schedule repeat. This value determines how frequently change detection occurs.
- That the notification threshold is configured appropriately based on the synchronization group interval. This value determines how frequently a user is notified of updated server cache data.