# Email Notification Redirect Anomaly **URL:** \ **Category:** SHF Discussion and Questions\ **Tags:** workflows\ **Created:** [December 30, 2022, 7:37pm UTC](https://developer.sailpoint.com/discuss/t/email-notification-redirect-anomaly/7321 "2022-12-30T19:37:05Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![bostelmann](https://avatars.discourse-cdn.com/v4/letter/b/aca169/32.png) [@bostelmann](https://developer.sailpoint.com/discuss/u/bostelmann)\ **Post date:** [December 30, 2022, 7:37pm UTC](https://developer.sailpoint.com/discuss/t/email-notification-redirect-anomaly/7321/1 "2022-12-30T19:37:06Z")
Hello All, I am not too sure if I am doing something wrong or if the outcome below is expected for the following scenario. When triggering a notification via workflows, while having the email redirect enabled, I have noticed the original recipient in the subject line will come through as _null_. I reviewed the output of the workflow test results and can confirm the email is being captured correctly and is not _null_. For example: ![Screenshot 2022-12-30 144005](https://global.discourse-cdn.com/sailpoint/original/2X/8/8ad3a3e8f58fb466fe045a601ba0afc431f26bfb.png) The same scenario using the standard email triggers, such as Lifecycle State Change, will populate the original recipient in the subject line. For example: ![Screenshot 2022-12-30 144154](https://global.discourse-cdn.com/sailpoint/original/2X/4/4fba856971f938c87aabac3b35ad9c7cabebd54b.png) Is this a defect or is my expectation incorrect? ---
**Author:** ![colin\_mckibben](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/colin_mckibben/32/37182_2.png) [@colin\_mckibben](https://developer.sailpoint.com/discuss/u/colin_mckibben)\ **Post date:** [January 3, 2023, 3:19pm UTC](https://developer.sailpoint.com/discuss/t/email-notification-redirect-anomaly/7321/2 "2023-01-03T15:19:22Z")
Hi Blaise, Just to clarify, are you using the “Send Email” action in Workflows? There is an open issue with engineering regarding this issue of null recipients, and it is currently being worked on. I will update this thread once a fix is in place. ---
**Author:** ![bostelmann](https://avatars.discourse-cdn.com/v4/letter/b/aca169/32.png) [@bostelmann](https://developer.sailpoint.com/discuss/u/bostelmann)\ **Post date:** [January 4, 2023, 3:03pm UTC](https://developer.sailpoint.com/discuss/t/email-notification-redirect-anomaly/7321/3 "2023-01-04T15:03:44Z")
Correct, I am using the Send Email action in the workflow. Is there a way I can find out more details about this defect? I would like to understand the extent of the defect a bit better. If we removed the email redirection would IdentityNow send the email to the actual recipient, or would it still fail because it believes the recipient is null? Is this a visual thing or an actual backend thing? Do we know when this will be resolved? ---
**Author:** ![colin\_mckibben](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/colin_mckibben/32/37182_2.png) [@colin\_mckibben](https://developer.sailpoint.com/discuss/u/colin_mckibben)\ **Post date:** [January 4, 2023, 3:30pm UTC](https://developer.sailpoint.com/discuss/t/email-notification-redirect-anomaly/7321/4 "2023-01-04T15:30:03Z")
There isn’t a way to track progress since it is an internal ticket. I reviewed the details of the ticket, and it appears that this defect is only present when redirecting emails to a test address. If you disable the test address option in the email config, then the original recipient should show up properly. There are a couple of proposed solutions. One is omit the “Original recipient” text from subject if it’s being redirected to a test address. The other option is to have an email show up in place of `null`. If there is a solution you prefer, I can forward your choice to the engineering team. ---
**Author:** ![bostelmann](https://avatars.discourse-cdn.com/v4/letter/b/aca169/32.png) [@bostelmann](https://developer.sailpoint.com/discuss/u/bostelmann)\ **Post date:** [January 4, 2023, 3:42pm UTC](https://developer.sailpoint.com/discuss/t/email-notification-redirect-anomaly/7321/5 "2023-01-04T15:42:23Z")
Awesome, thank you for the confirmation. My preference would be to have an email show up in place of the _null_. ---
**Author:** ![bostelmann](https://avatars.discourse-cdn.com/v4/letter/b/aca169/32.png) [@bostelmann](https://developer.sailpoint.com/discuss/u/bostelmann)\ **Post date:** [January 9, 2023, 1:53pm UTC](https://developer.sailpoint.com/discuss/t/email-notification-redirect-anomaly/7321/6 "2023-01-09T13:53:09Z")
As an update, it appears this issue has been resolved and is no longer occurring for me. ---
**Author:** ![colin\_mckibben](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/colin_mckibben/32/37182_2.png) [@colin\_mckibben](https://developer.sailpoint.com/discuss/u/colin_mckibben)\ **Post date:** [January 9, 2023, 3:34pm UTC](https://developer.sailpoint.com/discuss/t/email-notification-redirect-anomaly/7321/7 "2023-01-09T15:34:19Z")
You are correct. I just received notification from engineering that the issue has been fixed. ---
**Author:** ![system](https://global.discourse-cdn.com/sailpoint/original/2X/f/f2136700ed5e3703e0b85e02f6be799dacca7735.png) [@system](https://developer.sailpoint.com/discuss/u/system)\ **Post date:** [July 19, 2023, 2:24pm UTC](https://developer.sailpoint.com/discuss/t/email-notification-redirect-anomaly/7321/8 "2023-07-19T14:24:03Z")
Closed on July 19, 2023, 2:24pm UTC