Sync status
The sync status shows the sync summary and current status of users and groups of a provisioning connection.
Sync updates
Sync updates occur when there is a change at the source on a user, group, or membership if the target supports group provisioning. The provisioning service updates the user at the target and keeps the source and target in sync.
Sync frequency
Sync frequency depends on the provisioner and is not configurable.
For outbound provisioning, changes are near real-time. When there is a change to a user in PingOne, the target identity store is updated immediately.
For inbound provisioning with Workday, a polling mechanism checks the source identity store every 15 minutes. When there is a circuit breaker due to polling failure, the reset is 12 hours. After 12 hours, the polling mechanism will attempt to run a full re-sync for the associated provisioning rule. For LDAP inbound poll failure, the reset is 30 minutes.
Learn more about inbound and outbound provisioning in Inbound and Outbound Provisioning.
To see your sync status, see Viewing sync status.
| Identity store | Inbound | Outbound | Sync Frequency |
|---|---|---|---|
SCIM |
No |
Yes |
Real-time |
Salesforce |
No |
Yes |
Real-time |
Salesforce Communities |
No |
Yes |
Real-time |
Salesforce Leads and Contacts |
No |
Yes |
Real-time |
Aquera |
No |
Yes |
Real-time |
Workday |
Yes |
Yes |
Users are retrieved from the source identity store using a polling mechanism. For every subsequent update, polling occurs every 15 minutes. |
Microsoft Azure (Office 365) |
No |
Yes |
Real-time |
Zoom |
No |
Yes |
Real-time |
Slack |
No |
Yes |
Real-time |
ServiceNow |
No |
Yes |
Real-time |
Google Workspace |
No |
Yes |
Real-time |
GitHub EMU |
No |
Yes |
Real-time |
LDAP Gateway |
Yes |
Yes |
For inbound sync, users are retrieved from the source identity store using a polling mechanism. For every subsequent update, polling occurs every 2 - 3 minutes. For outbound sync is real-time |