# Identity Attributes Changes not Logged in Access History

**URL:** <https://developer.sailpoint.com/discuss/t/identity-attributes-changes-not-logged-in-access-history/194182>\
**Category:** SHF Discussion and Questions\
**Tags:** identity-security-cloud\
**Created:** [January 27, 2026, 5:47am UTC](https://developer.sailpoint.com/discuss/t/identity-attributes-changes-not-logged-in-access-history/194182 "2026-01-27T05:47:13Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![YanCoelho](https://avatars.discourse-cdn.com/v4/letter/y/f6c823/32.png) [@YanCoelho](https://developer.sailpoint.com/discuss/u/YanCoelho)\
**Post date:** [January 27, 2026, 5:47am UTC](https://developer.sailpoint.com/discuss/t/identity-attributes-changes-not-logged-in-access-history/194182/1 "2026-01-27T05:47:13Z")

</div>

> ‼ Please be sure you’ve read the [docs](https://developer.sailpoint.com/idn/docs/) and [API specs](https://developer.sailpoint.com/idn/api/getting-started) before asking for help. Also, please be sure you’ve [searched](https://developer.sailpoint.com/discuss/search?expanded=true) the forum for your answer before you create a new topic.

I had a case where changes to my identity attributes weren’t logged in Access History, and because of that, I believe my workflow was not triggered!

My “Work Email” attribute in the identity profile has a First Valid transform, which, at first, sets a default value for newly created identities. After the AD account creation, it gets the UPN value that was generated by a rule (standard pattern).

Today, while running a few tests with 200 accounts, I came across 20 accounts where the Work Email attribute was changed, but I couldn’t find the logs in the Access History.

And then I found this article: [https://support.sailpoint.com/csm/en/identity-attribute-update-not-showing-in-identity-history-or-search?id=kb\_article&sys\_id=091e8f3e33e96e908413a5373e5c7b53](https://support.sailpoint.com/csm/en/identity-attribute-update-not-showing-in-identity-history-or-search?id=kb_article&sys_id=091e8f3e33e96e908413a5373e5c7b53), which, for me, is really odd. After a few tests, it turned out not to be true!

I made tests with attributes that trigger provisioning actions and attributes that doesn`t, both cases were logged!

Has anyone come across this “issue”? This is the first time I’ve seen this, and it worries me a little bit.😅

---

<div class="post-metadata">

**Author:** ![Wegmannorth](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/wegmannorth/32/33587_2.png) [@Wegmannorth](https://developer.sailpoint.com/discuss/u/Wegmannorth)\
**Post date:** [January 27, 2026, 8:21am UTC](https://developer.sailpoint.com/discuss/t/identity-attributes-changes-not-logged-in-access-history/194182/2 "2026-01-27T08:21:52Z")

</div>

Hello Yan,

Yes, I have also come across cases when specifically AD-provisioning and sync jobs are not logged in ISC.

Are you seeing the changes in the VA?

Are you seeing the changes on the IQService host?

If not:

You could apply an AfterModify script to your AD-connector just to get the provisioning plans stored on sync. Here you can also filter on the Work Email attribute for example if that’s specifically what you want to log.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/sailpoint/original/2X/f/f2136700ed5e3703e0b85e02f6be799dacca7735.png) [@system](https://developer.sailpoint.com/discuss/u/system)\
**Post date:** [March 28, 2026, 8:22am UTC](https://developer.sailpoint.com/discuss/t/identity-attributes-changes-not-logged-in-access-history/194182/3 "2026-03-28T08:22:49Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.