Flow designer inbound email issue
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-12-2019 05:00 AM
Hello everyone, I am a relatively new developer to ServiceNow and am attempting to use the Flow designer to create records for a custom app based on inbound email.
In my test environment my flow works perfectly fine and the record is created.
The flow parameters are:
Trigger: Inbound Email
Email Conditions: Recipients contains "target email address"
Action: Create Record
Table - table created for custom app
Fields - Short Description > Subject | Description > Body Text
When I test my flow on my test environment I get no errors and the flow creates the record.
When I do the same test with the same email in my production environment I receive an error "Error: Exception occurred while evaluating flow triggers null"
There is no difference in the flows that I can see from one environment to the next.
Does anyone have any thoughts as to why I might be getting an error in my prod environment on a flow that works fine in my test environment?
Thank you
Matthew York
- Labels:
-
Scripting and Coding

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-12-2019 06:42 AM
Hello,
Was this developed on Test or in Dev? It's rather difficult to address how it works in one environment versus another, especially without any screenshots or script (if applicable) shown. The only thing I can say is attempt to create an update set, add that flow, then promote that to your Production environment and see if that resolves it. From that error messages, it's basically saying it can't use the flow trigger "null" which would mean where null is....it's not defined in that environment.
Please mark reply as Helpful/Correct, if applicable. Thanks!
Please consider marking my reply as Helpful and/or Accept Solution, if applicable. Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-12-2019 07:56 AM
It is probably against best practice but I did not design the flow in the dev environment and promote it to production. I merely designed it in production and attempted to test it and received the error.
After getting the error, I rebuilt the same exact thing in my dev environment and it worked fine.
I guess I am unsure what the "null" is referencing.
I attached a couple screenshots of the flow settings for both production and dev
Production settings:
Dev settings:
If there is something else I can provide, or if you have an idea of where I might even start to look for differences / settings that need to change please let me know the help is greatly appreciated.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-12-2019 10:35 AM
Hi,
One of them you have a trigger user record and the other trigger body text for the 3rd trigger. See the difference?
Please try to create them exactly the same and see if the issue still remains, then walk it along and change things.
Thanks!
Please consider marking my reply as Helpful and/or Accept Solution, if applicable. Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-14-2019 04:55 PM
Hello,
I switched around the Create Record fields section to match exactly the setup on my dev server and the flow is still not triggering. I continue to get the null error.