Free Trial

Alteryx Designer Desktop Discussions

Find answers, ask questions, and share expertise about Alteryx Designer Desktop and Intelligence Suite.

Batch Macro - "Temp Drive is getting full" error

tsnchan
7 - Meteor

Hello

 

I have the folloiwng Alteryx workflow with a Batch Macro. The purpose is to generate the rolling sum of the transaction amount for a sliding window with a width of 3 time steps. Here I only showed the Sliding Window, without the running sum part.

 

When I run the below workflow and the macro, I received error message "Temp Drive is getting full". I have tried to configure the Memory Limit of Alteryx (under Options ->  Edit User Settting) with a bigger size, still it did not work.

 

My machine has 58G hard-disk free space. Apparently, when I run this workflow / macro, it used up all the 58G. The dataset has 2M records, and its size is 51MB only. I tried to work with only the first 1M records, it works without problem. So it seems like it is a hard-disk space issue. I believe I did not build my Macro properly, therefore eating up so many disk space. And when I stopped the workflow, I get back my 58G hard-disk space.

 

Can anyone give some help? Thanks

 

Workflow and macro attached

 

Thanks a lot

tsnchan

 

 

12 REPLIES 12
tsnchan
7 - Meteor

Exported workflow without the input file

tsnchan
7 - Meteor

I am sorry, please ignore previous workflow package. Please use the following one version 6 instead. There was a bug before. Thanks a lot

tsnchan
7 - Meteor

The logic of the flow is like this.

 

The raw dataset contains a time series of money transactions between Originated Parties ('nameOrig") and the Destinated Parties ("nameDesc"). "Step" is the time step from 1 onward. Each step represents one hour. "Type" is the transaction type. In the workflow, I only want to look at "CASH_OUT", that's why I used a filter in the workflow to extract all "CASH_OUT" transactions. "Amount" is the transaction amount. 

 

The aim of the workflow including the Macro is to identify a sliding window of 100 hours so that we can do a rolling sum of the transaction amount, and rolling sum of the transaction counts for each nameDesc (Destination Party) afterwards. Please note that the workflow provided are only for identifying, for each nameDesc, the immediate previous time step of sliding window starting point up to the current row. To give you an example (see the attached png)

 

for nameDesc "C970", it has 15 transactions from step 9 to 236. "Sum_figure" is the number of transaction happened during the same hour (or same time step). Note that transaction did not happen each hour. Now, we want to find out the rolling sum of transactions for a sliding window of 100 hours. So, for the transactions of C970 done at timestep 131, its sliding window would start from 131-100 = 31, i.e. any transaction happened during the time frame from 31 to 131 (including both 31 and 131 will be counted). Therefore, the "sliding window edge" is defined to be the previous time step that C970 has a transaction, which is timestep 21. The Batch Macro is tasked to sort out the "sliding window edge" for each transaction of each nameDesc. 

 

I hope this explain my logic. Thanks.

 

 

 

 

 

 

Labels
Top Solution Authors