Welcome to the Alteryx Knowledge Base

The Run the Worker as a Different User a.k.a “Run As” option in the System Settings allows the Worker to run the Alteryx Engine as a different user. By default, the Scheduler runs using the Local System Account.

When accessing these other environments, credentials that have Admin rights are recommended. This removes any chance of workflow failure if permissions change for non Admin user.

 

Run as Different User:

 

• Scheduler: - If a Worker machine needs to run workflows that access files or data from a location that requires specific credentials to access it, the machine can be configured to run the workflows as a specified user or account.

 

• Server: - When clients are sending database connections to the Gallery, they will need to send the app to the Gallery that works with their system settings. Otherwise, the app will fail since it will not connect to their local instance of the database on their machine.

 

Alteryx > Options > Advanced Options > System Settings

 

 

Troubleshoot:

 

My workflow runs fine through the GUI but it fails through the Scheduler

 

This can be a sign of permission issues. For the workflow to run successfully it needs access to the resources it is referencing, such as network drives, files, and database connections. Check all of your Inputs and Outputs to verify whether the connections are local or remote (e.g. network drive). If you are connecting to a network drive, you may need to add a Run As user in the Alteryx System Settings (if one is not already present) in order for the Scheduler to adopt permissions.  
 

I have configured Alteryx Server to run workflows as a specified user, but they are failing.

 

You may be encountering this issue if the Worker machine that is configured to run the workflows as a specified user does not have the appropriate permissions in the workspace folder where files are stored. Double-click the System Settings icon on your desktop to open the System Settings window and check the following settings:

 

• Identify the Workspace folder specified on the Worker > General screen.
• Open Windows Explorer and navigate to that folder.
• View the folder properties.
• On the Security tab, verify that the user specified as the Run As user exists in the list of users. If it does not, add it.
• On the same tab, highlight the specified user and ensure it has the following permissions: Modify / Read & Execute / Read / Write.

I’ve set up the Run As and it has been working, but now my modules have started failing.

Check if the password has changed recently.