Automated Workflow Condition was not met but workflow executed

Lisa Blair

I created an automated workflow with the trigger to request a status from contacts in a cell on a bi-weekly basis if the following conditions are met. There were multiple requests sent to the contacts whose applications didn't have the Disposition listed below.

Is there a limit on the number of conditions in an automated workflow?

Insights and advice are most welcome.

Thank you,

Lisa

Paul Newcome

Are you able to show the data that was in the row(s) that incorrectly triggered the automation?

lanita.harless106241

Has there been any update? This is happening on my workflow as well. Adding screenshots below.

Genevieve P.

Hi @lanita.harless106241

I see you have your conditions set as OR, instead of AND. This means that if a row has a Full Progress and has a Cloud, but does not have "Declined" it will still show up because one of the conditions is met. Does that make sense?

lanita.harless106241

Hi Genevieve-- Ah! I feel silly. 😊 Thanks for the catch!

Lisa Blair

This wound up not being a SmartSheet error. It was mine, and I'll explain. As it turns out, there were TWO automations saved. One was this one shown here, and the other one, that appeared to be an error was saved on an old copy of a worksheet in an Archive folder.

Because the workflow in the archived file was still ENABLED, the process ran.

SmartSheet support noticed the issue when we compared a couple of emails and the associate noticed the emails were generated from different files. Kudos to SmartSheet support!

The resolution was to DISABLE the workflow on the archived file.

I hope this helps other folks to avoid making the same mistake.