Weird input issue

[Isha_Gupta]

i have 4 files which are getting input and then union in the start of the workflow.

The whole workflow runs in around 40 seconds, until last month.

This month I am facing a weird issue.

3 out of 4 inputs are stuck on 1% while 1 is stuck at 39% for forever.

When I remove 1 specific file ABC, the workflow runs in 20 seconds with 3 inputs, when I connect it back, it is back to stuck at above % for 3 files which were running without any issue.

When I input that specific file alone, it is again getting input in like 15 seconds.

That specific file isn't event too big, comparable to every month's file with around 200K records and the schema of each of the 4 files is exact same.

Any help or workaround without changing the combined input for union, will be appreciated.

[binuacs]

@Isha_Gupta use batch macro instead of the union tool

https://knowledge.alteryx.com/index/s/article/The-Ultimate-Input-Data-Flowchart-1583459854309

[Raj]

@Isha_Gupta you can use this Macro

[apathetichell]

I'm bucking the trend of "use a batch macro" and going with - can you compare the schema of the three files vs the fourth file using field info. Does the fourth file have a field with the same name but a different type?

I'd also go with "turn off amp."

[Isha_Gupta]

@Raj @binuacs 

Macro works pretty good, but how to save and send the updated workflow.

When opened after sending it, the macro converts to a question mark.

If exporting, which files to select as a package, considering inputs and outputs both gonna change.

[adhillon]

Hi there,

The macro becomes a question mark if the person that you are sending it to has no reference of it. I would highly suggest setting up a macro repository and ensuring that you and any users sharing macros are connected to the same one.

There is a useful KB here: https://knowledge.alteryx.com/index/s/article/Sharing-Macros-in-Alteryx-Designer-and-Server-15834616... 

In terms of what you want to package and what you do not, just select the macros and parts that you want to share with the other person. Alternatively you can leave it in there and they can replace the location path to what it needs to be. Again, if the data lives in a shared location, ensure that paths are relative in your workflow.

[Raj]

@Isha_Gupta if you are sending the workflow to other machine make sure you share the zip file 
so the next person also have the Macro

else if you are saving the macro to server make sure you check the correct boxes for workflow assets.

[binuacs]

@Isha_Gupta use the export workfow option to save the workflow and associated files including macro