Output Errors/.bak files

[sasif]

Hello,

I have two workflows in separate tool containers and I run them individually by only activating one container at a time. I am experiencing the following issues when outputting to the same file in both workflows:

1) My workflows are extremely slow, I am wondering if this is because the output file is large 110 MB

2) After running the first workflow in the tool container, running the second workflow gives me one of the errors below:

"Error: Output Data (11): Unable to create backup of ...... Access is denied. (5)

"Error: Output Data (6): Can't open file .......The process cannot access the file because it is being used by another process. (32)"

The output file is not open so I am guessing this may have something to do with the .bak files that are being created. I am assuming this is the reason why the file is "being used by another process"

Is there a way to disable the creation of the .bak files?

Thanks

[Manoj_k]

The .bak files created by Alteryx when writing to the same output file are causing the issues you're experiencing.

The best way to tackle this is to modify your workflows to use unique output file names. This avoids conflicts and allows both workflows to run independently without encountering the "access denied" or "file in use" errors.

[Manoj_k]

The .bak files created by Alteryx when writing to the same output file are causing the issues you're experiencing.

the best way to tackle this is to modify your workflows to use unique output file names. This avoids conflicts and allows both workflows to run independently without encountering the "access denied" or "file in use" errors. 

[CharlieS]

Hi @sasif 

You'll notice that those errors are coming from Output Data tools 6 and 11. If I had to guess, do your two containers each have an Output tool writing to the same file? It sounds like that's where the conflict is. Don't forget you can use Find (Ctrl+F) to look up tools by their ID numbers on the canvas)

Try using 1 Output tool for each file you're writing and use upstream tools to determine what to write to that file (the results from container 1 or container 2 for example, or both results union-ed if that works for your data)