Ouput to Hyper File "Locked in another process" error

Question

Hi all,

I have a workflow that I used to run in 2023.1 version of alteryx and the workflow ran without error for ~1 year. In December, we switched to 2025.1 and now the workflow errors when the output tool runs.

I have the output hyper file set up in a way that it overwrites the existing hyper file which is brought in with an input tool (see attached screenshot). The existing data in the hyper file input tool comes in (in this example say it has Jan'26 data only) and then I run the workflow to pull in Feb '26 data so that the new output will include Jan and Feb data. I believe the error is saying locked in another process because it's trying to have the input and output processing at the same time.

Again, prior to new version this process worked. I have the input/output in control containers which kept them separate before but now has error issues. Appreciate any support/troubleshooting.

Alteryx Screenshot.png

parkerschubert · Answer

Control containers require AMP Engine which I have those in the workflow. Should I remove the control containers? Block until done also can't be used in a control container?

TheMattLeonard · Answer

First things first, I agree with Danilang, turning off AMP Engine most likely will solve the issue (Canvas Settings --> RunTime --> CheckBox at the bottom).

If you still run into the issue, I have a work around.

* Instead of outputting to the same file you are inputting, add a Block Until Done Tool, attach the Output Tool to the first output node, and output to a standalone file that will act as a temporary home for the data. You can name it "TEMP" or something like that.
* Off the 2nd output node of the Block Until Done Tool, attach a Dynamic Input Tool and point it to the TEMP file that was just created.
* Have this Dynamic Input Tool go directly to another Output Tool that will write to the original file.

I haven't had any issues with inputting and outputting to the same file within a workflow, but I think no matter what, with this sequencing and use of a temporary output file should solve the problem.

danilang · Answer

Hi @parkerschubert

Have you tried running the workflow with AMP turned off?

Dan