- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-30-2023 05:57 AM
I've created a Flow Designer flow with an 'Inbound Email' Trigger
Once triggered, the flow Submits a Catalog Item Request
This works very well, unless the inbound email has a "Disclaimer message" in it.
Example:
"This message may contain confidential and/or privileged information..."
Then the flow gets an error and does not process.
I've noticed in the Execution Details of the flow that the Description, Requestor For, and Short Description do not get populated. (see attachment)
Any help would be greatly appreciated!
Thank you.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-06-2023 06:56 AM
This issue is resolved.
This KB/Problem was the issue:
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0994344
See attachment
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-30-2023 06:34 AM
Hi @Su522
Can you share the flow error logs not the one you shared, click on Open Flow Logs and share what you see.
Anvesh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-02-2023 04:28 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-02-2023 05:07 AM
The error log attached doesn't contain the info why the subject and description got extracted. Have you tried testing the flow manually against an email containing the disclaimer? And try checking the if the email is truncated or kind of thing.
Anvesh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-02-2023 05:14 AM
Hi
How can I test the flow manually against an email containing the disclaimer?
In the email logs I don't the email is truncated and the same email with the "Disclaimer message" works to create incident tickets.
Thank you,
Susn