I am working with a customer who has Designer + Desktop Scheduler with the scheduler running locally on the same computer as Designer. A workflow has been scheduled with Run Location as "Copy saved to Scheduler DB" and I would like to open the YXMD to view it in Designer. I am probably missing something obvious but how can I open the workflow? I can't find any information online on where the "Scheduler DB" actually lives within this type of setup, System Settings doesn't give me any clues, and searching through ProgramFiles/Alteryx gives no sign of my workflow.

How can I open a workflow saved to the Scheduler DB in a Designer + Scheduler environment?

I am working with a customer who has Designer + Desktop Scheduler with the scheduler running locally on the same computer as Designer. A workflow has been scheduled with Run Location as "Copy saved to Scheduler DB" and I would like to open the YXMD to view it in Designer.

copy saved in scheduler db.png

I am probably missing something obvious but how can I open the workflow? I can't find any information online on where the "Scheduler DB" actually lives within this type of setup, System Settings doesn't give me any clues, and searching through ProgramFiles/Alteryx gives no sign of my workflow.

setup type.png

Server

Scheduler

Accepted answers

KaneG

Just in case you didn't get there. I've attached your example also with how to get the actual module. You can edit the workflow as I probably have paths to my local files etc.

I also included the ServiceDataParser Macro which comes in handy for parsing many of these tables.

Connect to SQLite Tables with extract file.yxzp

All comments

lminors

Hi @jamielaird,

I am lead to believe the SQLite is stored somewhere like:

C:\ProgramData\Alteryx\Service\Persistence\

Have you tried looking in there?

The information here may also help you:

https://community.alteryx.com/t5/Alteryx-Server-Knowledge-Base/Query-Scheduler-Database-from-Alteryx/ta-p/10534

Hope this helps.

Luke

mbarone

Great question. I do not know the answer, but I will follow this thread to see if someone does. For me, I have Scheduler installed on my Server, as a Mongo instance. I searched my entire "\ProgramData\Alteryx" directory and found none of the YXMDs I put on Scheduler. I've always been under the assumption that you would need to go to the original module, update it, and save it back to Scheduler as a new schedule, and then delete the prior one.

But it makes sense that you should be able to grab it from somewhere in scheduler. The only thing I can think of is that Mongo picks apart the XML and stores it as Mongo objects. Still, I can't find the module by name either if I search our Mongo directory.

I'll be interested to see what others have to say. The parser and mongo inputs don't seem to tell you the location of the scheduled modules saved in database.

jamielaird

Thanks @mbarone.

@patrick_digan has published a workflow here that allows you to search the MongoDB for a particular YXMD when working in a Server environment, and if the file has indeed been pushed to the SQLite DB on the same machine as the Designer (as suggesed by @lminors) then perhaps a similar approach would work.

It feels like a bit of a hacky way to get hold of the workflow, so I thought there must be an easier way. The workflow was uploaded several months ago and has been happily running every day, but I'd be surprised if there isn't a way to access it without digging into the database.

Szabolcs

Hi,

Are there any solution to join As_Application with As_Queue and As_Result? Basically my problem that As_Application includes the workflow name and ROWID. AS_Queue inlcudes all usefull info like Status or creation date etc.. but if I join based on rowid the result is not what I can see in the scheduler. In As_Application there are 225 ROWID but in AS_QUEUE 12000.

Thank you.

Szabolcs

KaneG

Hi @Szabolcs,

I haven't played with this in a few years but hopefully the below is still correct

AS_Applications.Id (after the ServiceDataParser in the above workflow) may be the same as AS_Applications.ROWID, and it joins to AS_Queue.AS_Application__ID and AS_Queue.__ROWID joins to AS_Results.AS_Queue__ID

Quick Links

This months top contributors

atcodedog05 19598

Qiu 15878

binu_acs 15708

MarqueeCrew 13708

apathetichell 13703