We’re experiencing significant delays in succession planning data appearing in the Workday Mobile app. When managers update succession candidates or development plans in the desktop application, these changes don’t reflect in mobile for 45-60 minutes. This is causing confusion during talent review meetings where executives use mobile devices.
I’ve checked our mobile sync intervals which are set to standard 30-minute polling, but the actual lag is much longer. Push notifications for succession updates aren’t triggering at all. Our API polling frequency seems normal based on logs, but wondering if background sync settings might be interfering when the app isn’t actively open.
Has anyone dealt with mobile sync lag specifically for succession planning data? Need to understand if this is a configuration issue with sync intervals or something deeper with the API endpoint behavior.
Here’s a comprehensive solution addressing all the sync components:
Mobile Sync Intervals Configuration:
First, enable the ‘Accelerated Mobile Sync for Talent Data’ feature in your tenant configuration (Setup > Tenant Setup > Mobile Configuration). This reduces the succession planning data propagation window from 45-60 minutes to 5-10 minutes.
API Polling Frequency Optimization:
Update your mobile API polling settings to use adaptive polling for succession data:
PATCH /api/mobile/v1/config/succession
{
"adaptivePolling": true,
"minInterval": 300,
"maxInterval": 1800,
"prioritySync": ["succession_plans", "talent_cards"]
}
Push Notifications Setup:
Navigate to Setup > Mobile Application Configuration > Notification Services and enable these specific channels:
- Succession Plan Updates
- Talent Card Changes
- Development Plan Modifications
Ensure the notification service is connected to your push notification provider (APNS for iOS, FCM for Android).
Background Sync Settings:
The critical fix is enabling background sync for succession data. In Mobile Device Management policies or via the Configuration API:
PUT /api/mobile/v1/backgroundSync
{
"enabled": true,
"modules": ["succession_planning"],
"syncStrategy": "incremental",
"backgroundRefreshInterval": 900
}
Verification Steps:
- Test by making a succession plan change in desktop
- Monitor the mobile API logs for sync triggers
- Verify push notification delivery within 5 minutes
- Check that backgrounded apps sync within 15 minutes
The combination of enabling accelerated sync, configuring adaptive polling with priority for succession data, properly setting up push notifications, and enabling background sync should reduce your lag to under 10 minutes even when the app is backgrounded. The adaptive polling will increase frequency when changes are detected and reduce it during quiet periods to preserve battery life.
Thanks for the insights. I checked and the ‘Accelerated Mobile Sync for Talent Data’ feature is not enabled on our tenant. That could definitely explain the lag. However, I’m still unclear about the push notification configuration. Where exactly in the mobile app settings should I be looking for the succession planning notification channel? I’ve checked under Settings > Notifications but only see general talent management options.
For the API polling behavior, check this configuration:
GET /api/mobile/v1/succession/syncSettings
{
"pollingInterval": 1800,
"backgroundSyncEnabled": false
}
That backgroundSyncEnabled flag is likely your culprit. Also verify push notification registration.
The notification channels are configured server-side, not in the mobile app UI. You need to access the Workday tenant configuration under Mobile Application Configuration > Notification Services. There’s a specific setting for succession planning events that needs to be mapped to the mobile push notification service. Also worth checking your background sync settings - these are in the Mobile Device Management policies if you’re using MDM, or in the Workday Mobile Configuration API settings if you’re managing it programmatically.