# Account Request stuck at Pending state even after Provisioning **URL:** \ **Category:** IIQ Discussion and Questions\ **Tags:** access-requests, provisioning, identityiq\ **Created:** [January 13, 2026, 11:37am UTC](https://developer.sailpoint.com/discuss/t/account-request-stuck-at-pending-state-even-after-provisioning/193231 "2026-01-13T11:37:53Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![aakashpandita](https://avatars.discourse-cdn.com/v4/letter/a/71e660/32.png) [@aakashpandita](https://developer.sailpoint.com/discuss/u/aakashpandita)\ **Post date:** [January 13, 2026, 11:37am UTC](https://developer.sailpoint.com/discuss/t/account-request-stuck-at-pending-state-even-after-provisioning/193231/1 "2026-01-13T11:37:53Z")
IIQ version : 8.4p1 We have 2 AD applications. When an account request is submitted and provisioned, for one of the application the request shows **Execution Status: Completed** but for other application request it shows **Execution Status: Verifying** and is stuck there even after we run “Perform Identity Maintenance” task. I have checked docs and community and found few articles where this is happening because **pwdLastSet** attribute is stuck at committed and not changing **Finished** or **Not Verifiable**. Weird thing is both are AD apps and its happening for only 1 app and other one is working fine. we are setting value pwdLastSet to true in both apps. I could have resolved it by removing the **pwdLastSet** value from prov policy but we need user to reset password on next logon so we have to set this value during account creation. anyone faced this?? ---
**Author:** ![aakashpandita](https://avatars.discourse-cdn.com/v4/letter/a/71e660/32.png) [@aakashpandita](https://developer.sailpoint.com/discuss/u/aakashpandita)\ **Post date:** [January 13, 2026, 11:39am UTC](https://developer.sailpoint.com/discuss/t/account-request-stuck-at-pending-state-even-after-provisioning/193231/2 "2026-01-13T11:39:02Z")
the links I used to refer this problem: [https://community.sailpoint.com/t5/IdentityIQ-Forum/AD-account-created-but-access-request-shows-pending-status/m-p/163701#M133380](https://community.sailpoint.com/t5/IdentityIQ-Forum/AD-account-created-but-access-request-shows-pending-status/m-p/163701#M133380) ---
**Author:** ![sukarande](https://avatars.discourse-cdn.com/v4/letter/s/8edcca/32.png) [@sukarande](https://developer.sailpoint.com/discuss/u/sukarande)\ **Post date:** [January 13, 2026, 12:35pm UTC](https://developer.sailpoint.com/discuss/t/account-request-stuck-at-pending-state-even-after-provisioning/193231/3 "2026-01-13T12:35:24Z")
@aakashpandita . Can you try removing `pwdLastSet` from the policy for both accounts and update it in the After Provisioning Rule? Your question is valid; it should behave the same for both accounts. ---
**Author:** ![aakashpandita](https://avatars.discourse-cdn.com/v4/letter/a/71e660/32.png) [@aakashpandita](https://developer.sailpoint.com/discuss/u/aakashpandita)\ **Post date:** [January 13, 2026, 12:38pm UTC](https://developer.sailpoint.com/discuss/t/account-request-stuck-at-pending-state-even-after-provisioning/193231/4 "2026-01-13T12:38:15Z")
I can do all the customization I want and it will work I know that, but my concern right now is why its working for 1 AD app and not other. ---
**Author:** ![sukarande](https://avatars.discourse-cdn.com/v4/letter/s/8edcca/32.png) [@sukarande](https://developer.sailpoint.com/discuss/u/sukarande)\ **Post date:** [January 13, 2026, 12:41pm UTC](https://developer.sailpoint.com/discuss/t/account-request-stuck-at-pending-state-even-after-provisioning/193231/5 "2026-01-13T12:41:39Z")
@aakashpandita Can you compare plan for both account? there must be something slight difference. Also compare “Type Settings” and “Validation” for pwdlastset attribute from policy. ---
**Author:** ![aakashpandita](https://avatars.discourse-cdn.com/v4/letter/a/71e660/32.png) [@aakashpandita](https://developer.sailpoint.com/discuss/u/aakashpandita)\ **Post date:** [February 19, 2026, 11:31am UTC](https://developer.sailpoint.com/discuss/t/account-request-stuck-at-pending-state-even-after-provisioning/193231/6 "2026-02-19T11:31:30Z")
I ended up creating a task which checks and verifies pending requests once every day. ---
**Author:** ![santhirajumunganda](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/santhirajumunganda/32/42744_2.png) [@santhirajumunganda](https://developer.sailpoint.com/discuss/u/santhirajumunganda)\ **Post date:** [February 19, 2026, 12:18pm UTC](https://developer.sailpoint.com/discuss/t/account-request-stuck-at-pending-state-even-after-provisioning/193231/7 "2026-02-19T12:18:18Z")
does this mean the execution status is gone now for the other application? ---
**Author:** ![neel193](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/neel193/32/34038_2.png) [@neel193](https://developer.sailpoint.com/discuss/u/neel193)\ **Post date:** [February 19, 2026, 1:19pm UTC](https://developer.sailpoint.com/discuss/t/account-request-stuck-at-pending-state-even-after-provisioning/193231/8 "2026-02-19T13:19:20Z")
@aakashpandita You should not be needing a custom task to do that, IIQ should do it automatically for you. IIQ needs to validate the values of provisioned attribute against the schema attributes after aggregation. If there is a mismatch, then IIq will keep the request in Verifying state and eventually end with Not Verifiable state. So in your case, could you please confirm what is the value in provisioning vs after aggregation for both apps. ---
**Author:** ![aakashpandita](https://avatars.discourse-cdn.com/v4/letter/a/71e660/32.png) [@aakashpandita](https://developer.sailpoint.com/discuss/u/aakashpandita)\ **Post date:** [February 19, 2026, 4:40pm UTC](https://developer.sailpoint.com/discuss/t/account-request-stuck-at-pending-state-even-after-provisioning/193231/9 "2026-02-19T16:40:06Z")
The pwdLastSet value gets changed as soon as it is set in AD. From prov form we are setting it to 0 and as soon as account gets created AD sets it to its Windows timestamp. That is why Perform Identity Request Maintenance is not able to verify this attribute, sue to this mismatch. So I created a separate task to mark IdentityRequest as verified. ---
**Author:** ![neel193](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/neel193/32/34038_2.png) [@neel193](https://developer.sailpoint.com/discuss/u/neel193)\ **Post date:** [February 19, 2026, 5:58pm UTC](https://developer.sailpoint.com/discuss/t/account-request-stuck-at-pending-state-even-after-provisioning/193231/10 "2026-02-19T17:58:33Z")
Thanks @aakashpandita for the details. ---
**Author:** ![system](https://global.discourse-cdn.com/sailpoint/original/2X/f/f2136700ed5e3703e0b85e02f6be799dacca7735.png) [@system](https://developer.sailpoint.com/discuss/u/system)\ **Post date:** [April 20, 2026, 5:59pm UTC](https://developer.sailpoint.com/discuss/t/account-request-stuck-at-pending-state-even-after-provisioning/193231/11 "2026-04-20T17:59:19Z")
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.