Skip to main content
Nintex Community Menu Bar

Escalation emails fail to send out

  • February 24, 2022
  • 0 replies
  • 19 views
  • Translate

MillaZ
Nintex Employee
Forum|alt.badge.img+21
  • Nintex Employee
  • 675 replies
 

Escalation emails fail to send out

kbt138549

PRODUCT
K2 blackpearl 4.6.10
BASED ON
K2 blackpearl 4.6.10
TAGS
Escalations
This article was created in response to a support issue logged with K2. The content may include typographical errors and may be revised at any time without notice. This article is not considered official documentation for K2 software and is provided "as is" with no warranties.
LEGACY/ARCHIVED CONTENT
This article has been archived, and/or refers to legacy products, components or features. The content in this article is offered "as is" and will no longer be updated. Archived content is provided for reference purposes only. This content does not infer that the product, component or feature is supported, or that the product, component or feature will continue to function as described herein.

Issue

Escalation emails fail to send out and an error appears under Workflow Server > Error Profiles.

 

Image

Symptoms

  • The same error is found in the Host Server logs:

    "Error","General", "28083","ExtenderExecuteError","ProcessInstance.HandleException","28083 EscalationAction: There is no connection string for the  destination email address <Email Address>.
        InnerException: There is no connection string for the  destination email address <Email Address>."

 

  • There are no issues with email notifications from the Default Client Event and Email Event

 

  • The SMTP connection strings are correct

 

 

 

Troubleshooting Steps

This was resolved by re-creating the entire Activity where the escalation was configured on, and then re-deploying the Workflow.
Did this topic help you find an answer to your question?

Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie Settings