This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
Upon creating a BINGO game, I came across a technique that I thought could be useful in "real world" scenarios for users who are attempting to iterate a process and then replenishing the data after a certain amount of time.
Why did all of my scheduled workflows fail? What does the error “Logon Failure: unknown user name or bad password” mean?
This error is due to the credentials that are used for the scheduler are no longer valid and have most likely expired. To fix this, the Run As setting has to be updated in the scheduler machine. Someone with local admin rights to the machine should go to the System Settings (Alteryx > Options > Advanced Options > System Settings) then click Next until the “Run the Worker as a Different User” menu is selected and update those credentials.
Here at Alteryx we believe in working smart, not hard. Building out reports to highlight business-critical metrics is a pretty smart way to track goals. Customizing those reports to everyone in the department, then distributing them as attachments to individual emails? That sounds like a lot of hard work. Scheduling those reports from a refreshing data source each month so you don’t have to remake or rerun the reports yourself - that’s genius. Logging into your work computer to open up Alteryx, then having to check the scheduled results before having any peace of mind those reports were delivered without a hitch? Hard.
What’s the difference between Scheduling a workflow from its original location on disk vs as a copy in the Scheduler DB?
Run a copy of the workflow stored in the scheduler DB creates a copy of the workflow and stores it in the scheduler’s database. When the time comes to run the workflow, it is pulled up from the database and run.
When scheduling as a copy stored in the scheduler DB, it is important to make sure that any dependencies (input files, macros, etc) are available at run time. If the location of the dependencies cannot be reached by the Scheduler you may run into errors stating things such as “File not found” or “unable to open macro”. These errors mean the Scheduler is unable to see the file paths you have referenced in your workflow, and therefore cannot run the process successfully.
To get around these errors, check your dependencies. If you are using relative paths you may just need to set them to Absolute. You can do this by going to Options – Advanced Options – Workflow Dependencies.
When a workflow is stored in the database, it becomes static. Any changes made in Alteryx to this workflow are independent to the Scheduled version and will require you to upload a new instance of the workflow or replace the current one.
Run the workflow from its original location on disk calls the actual .yxmd file from where you originally saved it and runs the process.
You’ll still need to make sure the dependencies are accessible by the scheduler, including the location of the workflow itself.
The difference with this option is the scheduler is pulling the live version of the workflow and input files so any changes made are reflected the next time the workflow is run and there is no need to create a new schedule.
For more information on the Scheduler check out the Scheduler FAQ in the help documentation here.
On Alteryx version 10.1, if you try to schedule a workflow to to run from its original location on disk and the workflow path starts with a digit, for example C:\1testpath\workflow.yxmd, the workflow will fail to run on the Scheduler. When the job fails, you will see the job at the bottom of the Results view within the Scheduler window and the job date is January 01 0001 12:00:00 AM - this indicates a corrupt job. All other combinations work as expected.
This is a known issue that is being addressed. The workaround is to rename the folder so that the path does not start with a digit, for example C:\a1testpath\. Alternatively, you can schedule the job to run a copy of the workflow stored in the scheduler DB.