Re: [Form Mule Google Group] Re: Conditions Not Working, Please Help!

[Joseph Schmidt]

I'm confused. I only see merge template being sent. 

I'm only seeing two rows of data.  You can delete the status code and run FormRanger again while testing.

Joe Schmidt

 GLUA...@gmail.com

New Visions Blog Entry - Joe Schmidt

On Wed, Feb 16, 2022 at 1:44 AM Krystal Park <parkch...@gmail.com> wrote:

Here are some pictures to help illustrate the situation better.  I may be doing something that is fundamentally wrong so I also included pictures of a couple of conditions that I have tried.

On Wednesday, February 16, 2022 at 1:31:56 AM UTC-5 Krystal Park wrote:

Hi!

I currently have Form Mule trigger set up to send emails when a new google form is submitted. I have two distinct email templates however no matter how I phrase my conditions both emails get sent out regardless. 

When I check the preview, Form Mule seems to understand that the merge condition is not met for certain conditions and the send status is updated for the correct column. However, I continue to receive both email templates despite all this.

I would greatly appreciate any and all help in resolving this matter.

Thank you.

--
You received this message because you are subscribed to the Google Groups "NV Form Mule Add-on" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nv-form-mule-ad...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/nv-form-mule-add-on/00d52edf-8fb7-415d-be15-853c3e7f7a91n%40googlegroups.com.

[Krystal Park]

Right, although it says the faculty outreach template is being sent, I still receive both the faculty outreach and close contact outreach templates in my inbox. 

[Krystal Park]

Okay, I think I figured out what the problem was! The section for close contact outreach in my google form was not set up properly and led into the section for faculty outreach which may have confused the program. I made sure both sections were set to submit immediately after and it seems to have fixed the problem.