MyAlteryx
Community
Academy
Help Docs

Welcome to the Alteryx Knowledge Base

Knowledge Base / Designer / Alteryx Designer and Desktop Automation: Errors when running workflows using Python-based Conne...
Alteryx Designer and Desktop Automation: Errors when running workflows using Python-based Connectors
user

Created/Edited - 2/21/2025 by Clara Boo | Alteryx

Summary
Desktop Scheduler does not support the use of Python-based connectors
Issue

Running workflow containing Python-based connectors such as OneDrive, SharePoint, Google Drive in Desktop Automation/Scheduler fails with the following error:

Failed to authenticate

Screenshot of the error:

image.png
 

Another possible error as seen in ServiceNow connector: 
No permission -- see authorization schemes.
image.png
 
Yet another possible error as seen in the SharePoint Connector tools:
<class ‘AttributeError'>:’NoneType' object has no attribute 'get'
This image shows the error message: class AttributeError: NoneType object has no attribute get, when running the workflow in Desktop Automation.
Environment
  • Alteryx Designer
    • Version: All
  • *Python-based Connectors 
    • Microsoft OneDrive
    • Microsoft SharePoint
    • Microsoft Outlook 365
    • Google Drive
    • ServiceNow
*This is not an exhaustive list of connectors.
Cause

The credential information kept in the tool is user-encrypted. Running the workflow using a different user or local system account will not be able to decrypt it correctly hence the error.
 

Resolution

NOTE: Desktop Automation/Scheduler does not support the use of Python-based connectors. Please consider the use of the Alteryx Server instead.


If you do need to use the connectors in Desktop Automation/Scheduler, the workarounds can be one of the following:
  1. Set the "run as a different user" in Alteryx System Settings to the user who creates the workflow containing the connector.
 
image.png
 
  1. On the Desktop Automation/Scheduler machine, log on as the service account/user used in the "Run as a different user". Re-enter all the credentials information for the connector in the workflow and add it to the scheduler.
 
 
Additional Information
Was this article helpful?