Manually Pushing a Push Group Becomes Stuck on the Pushing Status
Last Updated:
Okta Identity Engine
Okta Integration Network
Administration
Overview
When manually pushing a Push Group to a downstream application, it becomes stuck on the Pushing status.
Applies To
- Push Groups
- API
- SCIM
- Provisioning
Cause
This usually occurs when the Group holds a large number of users. Depending on that number, the "pushing" process can run longer.
Solution
When a group push is queued, it needs to be completed before retrying; otherwise, the job will queue again and start once the previous job finishes.
Below are a few items we recommend checking:
- Ensure the same Group is not used for Application Assignment and Push Group.
- Ensure the users within the group are successfully provisioned to the Application from Okta.
- Verify that the users have External IDs in their User Application Profile.
- This can be verified by clicking the Pencil icon next to their name under the Assignments tab.
- Review the Group Push Common Issues article.
Please reach out to Okta Support if there are any questions or concerns.
