We've updated the ServiceNow Community Code of Conduct, adding guidelines around AI usage, professionalism, and content violations. Read more

Target filed is empty after processing email through Inbound Email trigger

HarshvardhanG
Tera Contributor

Hi Community,

I am facing an error while running the inbound email trigger "Value of filed record is not a GlideRecord". I am guessing the issue is because the inbound email's target record is empty. Attaching the screen shoot for reference.
Media (1).jpg

The scenario:
An event is triggered to user for this reply and links are added so when the user replies by clicking on the link a new email template will pop up with a specific to, subject, body and watermark. So once the ServiceNow received this email with the defined subject this flow will trigger and if it says approved then step 2 will update the target record with work notes but getting this error. 

3 REPLIES 3

Ankur Bawiskar
Tera Patron

@HarshvardhanG 

1st use Lookup Record to get that record and then use Update Record

💡 If my response helped, please mark it as correct and close the thread 🔒— this helps future readers find the solution faster! 🙏

Regards,
Ankur
Certified Technical Architect  ||  9x ServiceNow MVP  ||  ServiceNow Community Leader

@HarshvardhanG 

Thank you for marking my response as helpful.

💡 If my response helped, please mark it as correct and close the thread 🔒— this helps future readers find the solution faster! 🙏

Regards,
Ankur
Certified Technical Architect  ||  9x ServiceNow MVP  ||  ServiceNow Community Leader

pbusch
Tera Expert

Hi Harsh,

 

I started experiencing the same issue, and am actively troubleshooting.

I am on

Build name: Yokohama
Build date: 12-24-2025_1252
Build tag: glide-yokohama-12-18-2024__patch10-hotfix1-12-23-2025

 

Recreating issue:

1. If I 'Test' within Flow Designer test module, the selected sys_email passes sys_id correctly to nodes in my flow.

2. However, if sys_email table processes record [as per real world scenario], the sys_id disappears [see (2) in my first snip] [PFA1]

 

In my second snip [PFA2] the successful runs via Flow Designer 'Test' module all ran correctly with sys_id of the sys_email record selected for testing --- however, the top 3 feature the inbouund email processed through the normal email intake engine, and this is where sys_id becomes [nil] when a node in the flow attempts to reference it.

 

PFA3 is the blank sys_flow_email_trigger record associated to the Flow.

 

~ "Breynia Disticha"