Workflow dissociate from the Server after a save with a too long validation

[Keshrama]

Hello,

My company is running on Alteryx 24.1 and with Alteryx Server. Recently a problem liked with the saving of the Workflows on the server occured.

In the case of the error while saving "Validation is taking longer than expected", the Workflow then "dissociate" from the Server. Which means, if you save again your workflow, the save window for the server (with name of the WF, the studio, etc) won't open, the WF will be saved locally (in the temp file of Alteryx on the computer).

It happens only with validation taking too long and both when we wait for the validation to actually finish (by checking the WF server page) or not.

This problem could lead to mistakes in development if the owner doesn't notice that the saving was not the server type one.

I am open to advice and solution

Tahnk you very much in advance

[jrgo]

Hi @Keshrama 

Can't say why it disassociates, but whenever i've came across that message you pictured, when i navigate to the workflow on Gallery, I do see that it published and that the validation job is still in queue or running. Is that the case for you or is it both not publishing and disassociating?

You may also want to do some digging to see why the validation is taking too long. Even through a validation job generally run quick, it has to wait in a job queue if there's other jobs that are running or also waiting to run. If this is the case, you may want to uncheck the "Validate Workflow" option before you hit the publish button to skip that step. You server may also be in need of some additional capacity if there's an increase of users interacting with your Gallery.

If you don't think this is the case, you may want to look at the assets you're including when publishing the workflow. If there a connection to some external asset (database, network file, connector, etc) the validation could get hung up from it trying to test connectivity. Or you're reading from a really like Excel or CSV file and that is also being packaged with the workflow, that can also cause issues or long delays.

Hope this helps but if no one else has other ideas, i'd suggest your next step to submit a ticket to Alteryx's support as there could be other issues that is preventing Server from operating normally.

[apathetichell]

Hunch --- the user with the message has an earlier version than 2024.1. They are using a python/connector tool which uses python. It uses 3.8. Server is now on 3.10. Server says this is yucky.

[Keshrama]

Thank you for your answer. 

To clarify, all users are in 24.1 Alteryx Designer (the capture is older and just for presentation of the error i am talking of).

The validation is indeed continuing on the server and finishing there with no other problem. So it's just the WF on the designer side that dissociate but just the workflow, the server is still accessible to open another WF for example. 

The validation taking too long is only occuring for a few workflows that are quite huge. Uncheck the validation might indeed be a temporary solution to avoid mistakes and waiting for a solution/answer from Alteryx.

Thank you very much for your answer

[apathetichell]

ok. --- could just be workflow size. @jrgo 's answer is solid.