Input Files disappear from Flow folder

[RemcoV]

Hi all,

As a internal test phase for 25.1, I've downloaded the Admin version of 25.1, while using the non-admin version of 24.2 as our production default.

I am however encountering issues in using Alteryx version 25.1 when testing.

I have a workflow that uses two .yxdb files as an input. When I save my workflow to the server, I have selected to include them in the 'Manage workflow assets' option. So when I download the workflow from the server to Designer Desktop, the files are there in the same folder as my workflow itself (Not in any _External folder.

However, when testing. It seems that after a number of minutes, the input files are deleted from their location and my workflow errors because of it. 

Has anybody had this issue before? Or can anyone help me resolve it?

Thanks in advance!

Edit: It seems that not only my input files, but also the workflow file itself gets deleted from the Staging Folder. The only file left in the Staging Folder is a LOCK-file.

[BS_THE_ANALYST]

Hi @RemcoV. 

Is there a particular reason why you download the workflow from Server (is your server version 24.2?). Have you tried opening the workflow like so:

 

On a different note, when you download the workflow from Server to Designer, I assume this downloads as a .yxzp? 

What relation does the staging folder have to do with your local environment? I'd expect the staging folder to be cleared down unless you're directly interacting with the server. If you're downloading a workflow locally, the only relevant folder is local. Staging isn't being used by your local machine when you directly download a workflow

[RemcoV]

Hi @BS_THE_ANALYST ,

Apologies for the confusion, but I do in fact open the workflow like in your screenshot. 

I open workflows from the server in Designer with the same Version, being 25.1.

So there is no version offset between Designer Desktop and Server.

[Pilsner]

Hello  @RemcoV 

Great question, it's certainly got me thinking, so I'm eager to see others' responses. In the meantime, I have had a couple of thoughts which I've listed below:

When you say the files keep disappearing during testing, are you testing this on the server machine or on your personal machine?

I ask because, to my understanding, workflows on the Alteryx Server are stored in a compressed (zipped) format. When the server runs a workflow, it unpacks the workflow and any associated assets temporarily. Once execution is complete, the server clears these temporary unpacked files.

I would assume that, if at any point in this process you are accessing the workflow on the server machine, this could prevent the server from deleting the workflow itself, but won't stop it from deleting the input files, hence your workflow errors. Once you exit the workflow, I'm guessing the server is then able to clear it down, hence it too disappears.

I hope this helps. Please let me know if you have any questions.

Regards - Pilsner

[RemcoV]

Hi @Pilsner ,

I am testing the workflows on my personal machine.

Whenever I open my workflow from the server, and open the containing folder, I see the following:

As expected, I see my workflow and the two input files I use during testing. 

However, after a number of testruns and changes, the input files as well as the workflow file seems to be deleted form the containing folder. 

Regards, 

Remco

[Pilsner]

Hello @RemcoV 

After a little more investigation, I believe my previous statements about the temp/staging folder on the Alteryx server also hold true when opening a server workflow on your local machine. 

I have followed your steps of opening a server workflow on my machine, then opening the containing folder and as you can see, the workflow

and the related assets are all within a temp/staging folder. 

 

I'm not certain on the exact setting of this folder, but as this is in temporary storage, you would typically expect these files to be cleared down even if you save them to this location. 

I wouldn't typically expect files to clear down (disappear) without you closing to workflow but I believe there are a couple of things which could cause this to happen even with the workflow still open. One of these could be related to other processes on your computer. If you have other processes running on your computer and your computers memory is full, it may start clearing some data from the temp folder to free up some space. 

Although not the ideal solution, one way to get around the disappearing inputs would be to setup a network drive that both your machine and the server have access to. Then instead of packaging the inputs with the workflow, when you upload it to server, you just save it without any assets attached. The workflow will then reference the permanent files, stored on your network drive. Being outside of a temp folder, these should not clear down.  Alternatively, as soon as you open the workflow, copy the workflow and all its assets into a different saved location on your machine (just be awear you will need to re-upload the workflow if you make any changes using this method).

Regarding the workflow, I'm not quite sure how this can disappear whilst you still have it open. It will likely be deleted as soon as you close the workflow, as its only stored in the temp directory. 

Appreciate its not a definitive answer but I hope this is still helpful. Let me know if you have any other questions.

Regards - Pilsner

[jrgo]

Hi @RemcoV 

Behavior you're describing is certainly odd. While I don't have a solution for you, here's a few more things you can try and troubleshoot with:

• Do you experience this with other workflows or just that specific one?
• Do you have another machine with Alteryx 25.1 installed that you can try to see if it happens there as well?
  • Any of your colleagues who are also testing experiencing this?
• Do you have any other instances of Alteryx Designer open (not workflow tabs)?
  • If yes, are they other 25.1 or 24.2 Designer instances?
    • Does the issue continue if it's the only workflow and instance of Designer open?
• If you launch Designer as administrator, does this behavior continue?

Again, not a solution, but maybe this can help to narrow where the problem might be and determine if its a local system issue or a potential bug to report to Alteryx.

-Jimmy