Macro runs fine as a workflow but generates error when embedded into another workflow

Question

Hello,

I have a macro which runs fine as a standalone workflow (with no errors whatsoever). But when I insert it into another workflow to run as a macro, it always gets to about 2/3 of the way through, then generates this error message

The Designer x64 reported: InboundNamedPipe GetOverlappedResult: The pipe has been ended.

Note that I am using the same data for the macro inputs (regardless of whether the macro is being run standalone or as an embedded macro). The "outer workflow" (that contains the embedded macro) is extremely simple and consists only of the macro itself with the included input data (since I wanted to isolate the the root cause).

I built this macro on Alteryx Designer v2019.4 and it worked fine there. A few days ago, I upgraded to version 2021.3.54175 and I've been getting this error message. I did some web searching and it appears that this error is a generic error message, therefore I can't ascertain as to which part of the macro is failing.

To track the progress of the macro and try to identify which section was failing, I inserted "Count Records" tools throughout the canvas and noted their "Tool ID numbers". Then, I ticked "Show all macro messages" and ran the workflow, and I check the workflow log to see how far I was getting . To my surprise, all my "Count Records" tools were being processed successfully. So it isn't an issue with any one section specifically. I also did these steps for troubleshooting, none of which made fixed my issue.

* disabled all macro outputs

* disabled certain parts of the macro (e.g. disabling the last 10%, then the last 20%, then the last 30%)

* tried various "Output mode" options in the macro interface designer (CTRL + ALT + D)

* re-packaged the macro using Alteryx v2021.3 and then re-imported it

* duplicated the macro and saved it as a different name

Has anyone experienced this issue before? Thank you for your time.

Matt74192 · Answer

@mceleavey wrote:Hi @Matt74192 ,

can you provide the macro and some mocked up data so we can replicate the problem?

M

Hi @Mceleavey

i apologise for the delay in my response. i've done some more testing in the past few days and i've found that whenever the "Pipe has ended" error appears, the logs will show a message saying it can't find a certain tool. the most infuriating part is that whenever I run it, I can get any of the 4 outcomes below:

* the macro (standalone) does work
* the macro (standalone) does not work
* the macro (embedded into a broader workflow) does work
* the macro (embedded into a broader workflow) does not work

sometimes if I close and open Alteryx, the outcome changes. just when I think i have isolated the issue and am able to replicate, the outcome above would change.

here is an example of the error message which appears when scenario 4 above happens. i definitely don't have these tools in my workflow (be it the highest layer or all the underlying layers)

scenario 2

i didn't duplicate the error, the same line really did appear in my log file over 10 times !

00:00:45.908 - Error - ToolId 558: Can't find ToolId==558
00:00:45.908 - Error - ToolId 558: Can't find ToolId==558
00:00:45.918 - Error - ToolId 558: Can't find ToolId==558
00:00:45.918 - Error - ToolId 558: Can't find ToolId==558
00:00:45.974 - Error - ToolId 558: Can't find ToolId==558
00:00:45.974 - Error - ToolId 558: Can't find ToolId==558
00:00:45.974 - Error - ToolId 558: Can't find ToolId==558
00:00:45.974 - Error - ToolId 558: Can't find ToolId==558
00:00:45.974 - Error - ToolId 558: Can't find ToolId==558
00:00:45.974 - Error - ToolId 558: Can't find ToolId==558
00:00:45.975 - Error - ToolId 558: Can't find ToolId==558
00:00:45.975 - Error - ToolId 558: Can't find ToolId==558
00:00:45.975 - Error - ToolId 558: Can't find ToolId==558
00:00:45.975 - Error - ToolId 558: Can't find ToolId==558
00:00:45.975 - Error - ToolId 558: Can't find ToolId==558
00:00:45.975 - Error - ToolId 558: Can't find ToolId==558

Scenario 4

00:02:21.941 - Error - ToolId 3677: You have found a bug. Replicate, then let us know. We shall fix it soon.
00:02:21.941 - ToolId 3677: 0 records were output (ended by a downstream tool)
00:02:22.438 - Error - ToolId 3680: You have found a bug. Replicate, then let us know. We shall fix it soon.
00:02:26.360 - Error - ToolId 3680: Can't find ToolId==3680
00:02:26.360 - Error - ToolId 3679: Can't find ToolId==3679
00:02:26.865 - Error - ToolId 3679: You have found a bug. Replicate, then let us know. We shall fix it soon.
00:02:27.420 - Error - ToolId 3679: You have found a bug. Replicate, then let us know. We shall fix it soon.
00:02:27.927 - Error - ToolId 3679: You have found a bug. Replicate, then let us know. We shall fix it soon.
00:02:28.642 - Error - ToolId 3679: You have found a bug. Replicate, then let us know. We shall fix it soon.
00:02:29.206 - Error - ToolId 3679: You have found a bug. Replicate, then let us know. We shall fix it soon.

i will need to significantly amend my workflow prior to sharing with you, because there are various In-DB connections (that obviously won't work when you try to use it) so I'll have to convert them to dummy data.

In the meanwhile, have you come across those error messages above before?

Thank you, kind regards.

mceleavey · Answer

Hi @Matt74192 ,

can you provide the macro and some mocked up data so we can replicate the problem?

M