Skip to main content
Nintex Community Menu Bar

Hi All - I do not have a coding background and build quite basic approval workflows for use in my workplace.

I have configured workflow to send email notification as well as various flexi-tasks. This workflow is still in development and has been working perfectly for about a month now until last night I began getting the following error message:


"Failed to send notification. An invalid character was found in the mail header: ':'."

19766iE4FAFDE123A497FF.png19765i86870DAB3DCED803.png19767i2F7BC9BC97B08D9A.png

 

Nothing changed at all in the workflow actions to result in this error - merely continuing to test run submissions through the workflow. I have attached screen shots of how this is playing out in real time.

 

I have tried the following mitigation thus far that have all failed:
-removing references from the email subject

-removing references from the email body

-deleting the first send notification action altogether and placing my Management Approval flexi-task as the first  workflow action and still get the same error message - but the workflow says it is "in Progress" - no email was actually sent at this step and still got the workflow error message (shown below)

19769i80CAB07BF4330AC3.png19768i924A3E69AE0D9A99.png19770iAA68B6E92509F887.png

 

 

 

I do not have access to the nintex global admin for my workplace and am actively trying to figure out how to get into the settings to see if there is something that can be done?

I have 2 other workflows in use currently that launched for production on July 27. They have been running smooth without this issue thus far; however, I checked on one of the 2 workflows and there has actually been an instance of this same error message. (error shown in screen shots below) yet other requests around the one failure on the same version of the workflow are completing fine.

19772iE9B570C7B87D0114.png19773i7712EB5EFA10AD4D.png19771iC9A5C714A7D23AC1.png19774i5D049C0B4C9F59EB.png

 

 

someone please help!!

I have the same error, were you able to solve the problem

Reply