Okta Push Group Remains in Pushing Status During Manual Push
Last Updated:
Overview
When manually pushing a Push Group to a downstream application, the status indicator gets stuck on "Pushing". This occurs when a Push Group containing a large number of users remains in the Pushing status for an extended period. Resolve this issue by allowing the queued job to complete and verifying the group configuration, user provisioning status, and External IDs.
Applies To
- Okta Identity Engine (OIE)
- Okta Classic Engine
- Push Groups
- Application Programming Interface (API)
- System for Cross-domain Identity Management (SCIM)
- Provisioning
Cause
This behavior typically occurs when the Push Group contains a large number of users. The pushing process requires additional time to process large group memberships.
Solution
Why does the Push Group remain in the Pushing status?
When Okta queues a group push, the job must complete before initiating a retry. If a retry occurs before completion, Okta queues the job again and starts it only after the previous job finishes.
The Following Steps Verify the Push Group Configuration and User Statuses
Verify the group configuration, confirm successful user provisioning, and check for External IDs in the user application profile by reviewing the following items.
- Ensure the configuration does not use the same group for both application assignment and Push Group.
- Ensure Okta successfully provisions the users within the group to the application.
- Verify that the users have External IDs in their user application profile. Verify this by selecting the Pencil icon next to the user name under the Assignments tab.
- Review the Group Push Common Issues article.
