You are viewing limited content. For full access, please sign in.

Question

Question

Workflow not sending email anymore

asked on August 14, 2015

I have a workflow that starts when there is an entry change in the system, and looks through all entries to see if they meet certain criteria, and if so, it sends an email. 

My settings in the Workflow Designer are correct, meaning it sends me a test email. But the workflow is no longer sending emails. 

I have changed a field that was referenced in the workflow, and updated all references to this field in the Designer.

There are no errors or messages about email in the Messages queue. 

workflow.PNG
email workflow element.PNG
starting rule 1.PNG
starting rule 2.PNG
Connection Profile.PNG
email test.PNG
Completed.PNG
details.PNG
messages.PNG
qualifying document.PNG
workflow.PNG (88.09 KB)
email test.PNG (124.4 KB)
Completed.PNG (23.73 KB)
details.PNG (84.59 KB)
messages.PNG (84.39 KB)
0 0

Answer

SELECTED ANSWER
replied on August 14, 2015

You'd want to look at the mail server then. If the workflow completed successfully, then the mail server didn't return an error, so as far as WF can tell, the message was sent.

0 0

Replies

replied on August 14, 2015

Thanks Miruna. 

Can you believe, I had an extra space in my field value. It couldn't see the value "...Approval > $1,000" because I had the field as "...Approval  > $1,000". 

I just ran the workflow manually and it sent me an email. 

email.PNG
email.PNG (13.68 KB)
0 0
replied on August 14, 2015 Show version history

Now, though, I have a question about my starting rule.  Are there parameters about how often a Starting Rule based on "Entry Changed" will run? It seems like it should work every time, but it is not. If I change the "Approval" field to "Denied" and save the file, and then change it back to "Approved," I would expect it to kick off the workflow. Is this unreasonable? What should I expect?

 

 

Also, it seems like searching through the whole repository every time there is a change to an entry could get fairly unwieldy fairly quickly. What would be a good way to streamline this workflow so it would notice when those fields changed, but only run its processes on the actual entry that it noticed changing?

replied on August 14, 2015

Every entry change event is checked by the Subscriber to see if it satisfies the starting conditions. Take a look at the Subscriber Trace to see how events are evaluated.
 

You are not allowed to follow up in this post.

Sign in to reply to this post.