# Standard service before provsioning rule

**URL:** <https://developer.sailpoint.com/discuss/t/standard-service-before-provsioning-rule/81301>\
**Category:** SHF Discussion and Questions\
**Tags:** identity-security-cloud\
**Created:** [September 16, 2024, 1:03am UTC](https://developer.sailpoint.com/discuss/t/standard-service-before-provsioning-rule/81301 "2024-09-16T01:03:51Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![shekhardas1825](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/shekhardas1825/32/20889_2.png) [@shekhardas1825](https://developer.sailpoint.com/discuss/u/shekhardas1825)\
**Post date:** [September 16, 2024, 5:40am UTC](https://developer.sailpoint.com/discuss/t/standard-service-before-provsioning-rule/81301/5 "2024-09-16T05:40:50Z")

</div>

@kani Can you check with one of the user for which you did not provide any access (entitlement) from SailPoint request center? what I am assuming is, may be it is happening because of sticky entitlement as I have mentioned in your other post.

[Identity Refresh in IdentityNow - Identity Security Cloud (ISC) / ISC Discussion and Questions - SailPoint Developer Community](https://developer.sailpoint.com/discuss/t/identity-refresh-in-identitynow/80878)

If not, please check if the account is getting deleted in the target end before running the aggregation. What might happen is may be account is getting delete from ISC but not from target and in next aggregation it is bringing it back.

---

_[View the full topic](https://developer.sailpoint.com/discuss/t/standard-service-before-provsioning-rule/81301)._