I am seeing some strange things happening with the Alteryx Scheduler, which always fails without explanation when I run 'on disk'. To begin I'll explain my set up: * I'm using 10.1 * Server/Scheduler is set up on a Virtual Machine * I login to the virtual machine using a service account * The service account is also set up in the System Settings as Run the Worker as a Different User * I can run the workflow on the VM manually while logged in as the service account * I can run the workflow in the Scheduler DB * I can't run the workflow on disk - it errors * The workflow I'm trying to schedule has no references to any network drives and no macros, only the local machine is referenced * Sadly I can't upload pictures into this forum to show the results (Idea was raised in the forum improvements area), however they're similar to what is shown at this discussion with a few differences: http://community.alteryx.com/t5/Setup-Configuration/Scheduler-Results-Status-Corrupted/td-p/8475* Mine doesn't report Corrupted, it reports Error - VM Name * It is scheduled by the service account * The date completed is also January 01, 0001 12:00:00 AM * When I click on the Output of the scheduler results it gives no information, there are 2 messages:* Started running at * Finished running in 0.0 seconds Anyone have any ideas how I can rectify this? Note I'm developing in an enterprise environment, it is a requirement to schedule workflows on disk.

On Disk scheduler fails without explanation

I am seeing some strange things happening with the Alteryx Scheduler, which always fails without explanation when I run 'on disk'. To begin I'll explain my set up:

I'm using 10.1
Server/Scheduler is set up on a Virtual Machine
I login to the virtual machine using a service account
The service account is also set up in the System Settings as Run the Worker as a Different User
I can run the workflow on the VM manually while logged in as the service account
I can run the workflow in the Scheduler DB
I can't run the workflow on disk - it errors
The workflow I'm trying to schedule has no references to any network drives and no macros, only the local machine is referenced
Sadly I can't upload pictures into this forum to show the results (Idea was raised in the forum improvements area), however they're similar to what is shown at this discussion with a few differences: http://community.alteryx.com/t5/Setup-Configuration/Scheduler-Results-Status-Corrupted/td-p/8475
- Mine doesn't report Corrupted, it reports Error - VM Name
- It is scheduled by the service account
- The date completed is also January 01, 0001 12:00:00 AM
When I click on the Output of the scheduler results it gives no information, there are 2 messages:
- Started running at
- Finished running in 0.0 seconds

Anyone have any ideas how I can rectify this?

Note I'm developing in an enterprise environment, it is a requirement to schedule workflows on disk.

Error Message

Server

Scheduler

Accepted answers

AndrewW

I think I've found the problem that was preventing the workflow from running 'On Disk'. The file path of the workflow was \0Alteryx\...\workflow.yxmd. What I've discovered is if the first folder in the directory was renamed, removing the 0 at the start the workflow will then run 'On Disk'.

Therefore I can only assume a workflow can't be scheduled 'on disk' if the name of the first folder in the directory begins with a digit.

If anyone else out there is using the scheduler it would be interesting if you could test this, renaming the first folder in your directory with a number and see if you can schedule the workflow 'on disk'.

All comments

AndrewW

Therefore I can only assume a workflow can't be scheduled 'on disk' if the name of the first folder in the directory begins with a digit.

RodL

Andrew,

I took a working workflow and copied it to a folder called Test. I then ran it successfully through the Scheduler using the 'on disk' option.

I then renamed the folder to 0Test (which made it the first folder in my directory) and reran it successfully. So unfortunately not able to duplicate your issue.

Rod

mbarone

I am having this same issue. My folder is "M:\Flex_Errors\Weekly_Export". Anyone know what the root cause was aside from the foler having a number since this is not the case for me?

Thanks.

mbarone

After testing various reasons why this might be happening for me, it is because the server machine does not have access to some of the shared drives in the module. I will post an idea to have functionality added like there is for the Gallery----set individual modules to "run as" for Scheduler (so that each module can be have a different "run as", just like the Gallery). Note that I am aware I can set the server to "run as" a user, but I don't want all modules on Scheduler to refer to this. In other words, the Scheduler "run as" (system settings) is all or nothing, whereas the Gallery is per module.

Quick Links

This months top contributors

atcodedog05 19458

Qiu 15866

binu_acs 15708

MarqueeCrew 13708

apathetichell 13703