Attributes sometimes return null when writing to external systems

Feedback Bugs
1

I have some SailPoint workflows and PowerShell scripts that automatically fetch identity data during certain triggers (either for a daily task or on lifecycle state updates). One thing I am consistently noticing is certain identity attributes get written as null from both the PowerShell script and the workflow HTTP action. I have validated against the identity data in SailPoint, which every time has had non-null data.

A more concrete example is I use PowerShell to write first name, last name, and end date upon the lifecycle state moving to inactive. First name and last name never appear as null but sometimes the end date does. I don’t think this is a race condition pertaining to the endDate & inactive state trigger, as I have observed this same inconsistent behavior when fetching displayName from a SailPoint workflow.

In both instances, I am writing this data to a Jira ticket (on prem and in cloud). I think there is a bug within the product that returns null data consistently when the identity data being pulled is non-null.

2

Hi @dominick-miller,

Is there any specific filter you are using in your workflow to trigger the flow that you have mentioned in your use-case.

If you can share the same that may help to validate. I have faced few inconsistency but it was related to cache or some update issue.

Thanks