Recent Upgrade to 2025.1 Issues

Question

Hi Team, I recently updated my Desktop Automation environment to 2025.1 and two issues have sprung up I'm hoping you can assist with.

1.

I am running desktop automation. If I open the 'View Schedules' window I can see

-The Workflows listed in the Workflow tab

-Nothing is listed in the Schedules Tab   <----- Issue

-When workflows are running I can see them in the Queue tab

-I can see the output of the workflows in the Results tab

2. The Service Data Parser Macros (I've previously posted about these breaking after upgrading) https://community.alteryx.com/t5/Alteryx-Server-Discussions/ServiceDataParser-for-Version-2024-2-1-14/td-p/1338126

Getting the following message this time

ServiceDataParser (230) Tool #3: The plugin "C:\Program Files\Alteryx\bin\plugins\AlteryxService_Client.dll" could not be loaded: The specified module could not be found. (126) but the file exists in that location.

RogerNorthup · Answer

I don't run the Alteryx Desktop Scheduler, so my issue with the 2025.1 non-admin installation is that it just doesn't want to install.

It goes through a long check of system resources, then starts installation, but about 1/2 through, it reverts to "rolling back" installation and gives a note saying there's an error on my computer, but doesn't specify what it is.

In the meantime, it has removed my 2024.2 installation, which means I have to reinstall it, plus the patch, to get back to work.

And just to be petty, it also won't let me mute the "New Version Available" bar for any time other than the current session. So, it's always in my face, reminding me of what I can't have.  The same thing is happening to my coworker in another state.

Eknath_Alteryx · Answer

For the Point 1 reported with respect to the Schedules missing in Alteryx Desktop Scheduler after the Upgrade from 2024.2 to 2025.1 based on the Alteryx Case #00768503 , this is a "Defect" termed in the Current Version of Alteryx Designer 2025.1.

Also, just to confirm that this is now a known issue in Alteryx Designer 2025.1 as well where we have filed a defect internally - GCSE-3296 for the same.

This issue happens or was observed specfici  to the old schedules that are created via Alteryx Desktop Scheduler only.

Newly created schedules does not have the issue as they display abosolutely fine after creating them with the Alteryx Designer 2025.1 version.

This specific issue stems from a change introduced in Alteryx Designer 2025.1, where the ClientType value was redesigned to be explicitly set as "Designer". In older versions, this value was left blank, and the product did not automatically update existing records during the upgrade. As a result, previously scheduled workflows without a defined ClientType are not recognized properly in the updated Designer version, leading to the behavior you're seeing.

A workaround is to update the AS_Schedules SQlite DB file and update the ClientType.

Please find the below Workaround documented steps which I have prepared with the detailed instructions and please ensure to have a full backup of the database files prior making any changes after the Upgrade to 2025.1 version.

Work around instructions for Defect TGAL -13226 - Unable to view Schedules Post Upgrade 25.1 - Designer Desktop Automation

* Install SqliteStudio from → SQLiteStudio
* Click on Add a Database

* Select the AS_Schedules SQlite DB file and click OK

* Default :- C:/ProgramData/Alteryx/Service/Persistence/AS_Schedules/__TheData.sqlite

* Open SQL Editor

* Execute the SQL Command SELECT * FROM TheData to list all the records in the DB
* Execute the update command to update all the records of ClientType to Designer
UPDATE TheData

SET ClientType = 'Designer';

* Execute the SQL Command SELECT * FROM TheData and check if all the records are updated
* Open Designer and verify all the Schedules are now visible again.

______

For Point 2, Please log a support case with Alteryx for investigating further in house.

FkeetGuy · Answer

No response, I finally submitted a ticket via support. I also ran into another issue where I didn't have the correct license to use the 2024.2 version of Data Cleanse or the Unique tool.

Instead I've rolled back to 2024.2.