Macro Error: The output connection was not valid

Greetings.

I have a new macro based on the community message titled: "CS Macro Dev: Conditional Processing with Detours"

I do not get how to resolve the error shown below. Note I have the tools built into my original workflow and am attempting to substitute the macro in place of them. Any help is greatly appreciated.

Workflow Example: (Includes Detour tools the macro is to replace)

MACRO

MACRO Configuration:

DetourWorkflow Macro.yxmc

Macros

Accepted answers

MSalvage

@rgusaas,

I could be wrong, but it looks to me like this macro isn't doing anything at all... You need a macro input to actually run your data through the detour tool.

Even then I'm not sure this is going to do what you want. Batch macros run the entire data stream through a certain number of times based on the control parameter. So, I think you will want that to be a single value. Again, I could be wrong.

Either way I think the error is being triggered because you have no data flowing through the macro.

Hope this helps,

MSalvage

All comments

MSalvage

@rgusaas,

I could be wrong, but it looks to me like this macro isn't doing anything at all... You need a macro input to actually run your data through the detour tool.

Either way I think the error is being triggered because you have no data flowing through the macro.

Hope this helps,

MSalvage

rgusaas

I see your point regarding the macro.

MSalvage

@rgusaas,

Interesting. So the reason this error is actually being triggered is because the detour tool does not continue processing on the inactive side. Meaning it doesn't even pass 0 records. It is almost as if the unused macro output didn't have a connection. I would recommend using a 'Detour End' tool to bring the two streams back together and using a single Macro Output.

Best,

MSalvage

svora

Hello!

I build a batched macro and then put that macro in my main workflow, and it worked the first few times and now I get an error saying "Record #1: Tool #5 Parse Error at Char(53): Unknown Variable "#1" ... output connection "Report_Date Macro" was not valid" .... how can the workflow work most times and not now? Anyone get this type of error before?

Thanks for any insight!

Sabeen Vora

Alteryx MACRO Workflow - Snapshot.PNG Alteryx Workflow - Snapshot.PNG

Quick Links

This months top contributors

atcodedog05 19458

Qiu 15866

binu_acs 15708

MarqueeCrew 13708

apathetichell 13703