Running macro from workflow runs differently than running the macro itself

[luukve]

Hi all,

I have a standard macro which has one input row, containing two columns (a table name and an ID). 

I don't know if this is relevant but the macro contains, among others, a Dynamic Input tool which I use to delete records from a SQL Server table. 

In the SQL Editor of this tool I have this query:

"Select 1; Delete From [table] Where <condition>;"

In the tool configuration, I then replace the string [table] with the table name that I have as input of my macro, and <condition> is replaced by a WHERE clause which I generate inside the workflow.

Now, when I run this macro in isolation for a particular table name and ID, it executes the query 115 times (one for each WHERE clause that I have generated). It continues one and does some more stuff. All fine. Takes around 15-20 minutes to finish. 

However, here's the problem: when I invoke the macro from another workflow, with the exact same table name and ID, I see that it only executes the query 2 times, and stops after 3 minutes. 

Does anyone have any idea why there's a difference between running the macro on its own and invoking it, even though the parameters are exactly the same?

[luukve]

That solves it. Thank you!

So Alteryx recognizes only the first input is taken, and won't do any more processing as it will be filtered out anyway. 

Kind of dangerous, as the query that is executed doesn't just return a value, it also performs deletions.