Why are multiple "Send Email" blocks forcing all input fields to be required?

lindseyw
lindseyw Member
edited January 8 in Workflows

Hello! I am working on a workflow that has 3 parallel loops that will send emails. I added the first "Send Email" function to the first loop and was able to enter only the fields that I needed to (Recipient Emails, Body, and Subject), but when I tried adding the second "Send Email" function in the second loop, and all the input fields are required.

I checked and the first "Send Email" block still works just fine and does not require all of the fields.

workflow_help.png

UPDATE: I ended up breaking the workflow into 3 separate workflows and the issue is remaining! The first workflow is allowing me to save without all of the required inputs, but the other blocks (in totally different workflows) will not let me deploy without entering information into all the fields.

Tagged:

Best Answer

  • GrantSmith
    GrantSmith Coach
    Answer ✓

    I'd recommend logging a support ticket for this issue.

    **Was this post helpful? Click Agree or Like below**
    **Did this solve your problem? Accept it as a solution!**

Answers

  • GrantSmith
    GrantSmith Coach
    Answer ✓

    I'd recommend logging a support ticket for this issue.

    **Was this post helpful? Click Agree or Like below**
    **Did this solve your problem? Accept it as a solution!**
  • NCRivera
    NCRivera Member

    I just discovered I have the same issue now as well. I have a previous workflow that doesn't require all fields and when I created a new workflow, all fields are now required. When you navigate to code engine, it seems like not all fields are required and you're able to set any fields you don't need as null when testing.

Categories