Workspace Execution Tips and Troubleshooting
Before you save a Designer Desktop workflow to your Alteryx One workspace, review its connections, network dependencies, file paths, and required tools and drivers. A workflow that runs successfully on your computer can still fail in Workspace Execution because the execution environment has different access to data and resources.
Use this page to prepare an existing workflow, test it in Workspace Execution, and troubleshoot common migration errors.
Before You Begin
Workspace Execution is automatically enabled for new workspaces. Identify a Workspace Admin who can help configure Environment Customization, and coordinate with the administrator responsible for Data Bridge if your workflow accesses private network resources.
Saving a workflow to your library creates a new version. If needed, you can restore an earlier version of the workflow after you change its connections or tool configurations.
Review Workflow Dependencies
Inspect the workflow and any macros it uses. Record the dependencies that require changes before you save the workflow to Alteryx One:
Data connections and credentials, including connections in Input Data and Output Data tools.
Email tools and workflow events.
Connections inside embedded macros.
In-Database tools and their connection files.
API tools, including tools that connect to Alteryx Server.
Shared drives, UNC paths, and network file outputs.
Custom ODBC drivers, custom Alteryx tools, and older connector tools.
For each dependency, identify whether it requires DCM, Data Bridge, a different storage location, or Environment Customization. A single connection can require more than one of these changes.
Configure Connections with DCM
Use Data Connection Manager (DCM) for all connections in the workflow before you save it to an Alteryx One workspace. Review the entire workflow because connections can also exist in events and macros.
Review Input Data, Output Data, and Email tool configurations. Replace legacy connections with DCM connections.
Review workflow events. Convert connection settings to DCM where supported, or remove events that you no longer need.
Open embedded macros and review their connections. Update any remaining legacy connections.
For Email tools or email events, verify recipients and other email settings after you change the connection.
Nota
Review In-Database connections separately using the guidance in Configure In Database Connections.
The DCM Migration Tool can help identify connections to convert. If the tool reports that no suitable connections were found but saving to Alteryx One still produces a non-DCM connection error, manually inspect the workflow. See Non-DCM Connection Error under Troubleshooting.
Configure Access to Private Network Resources
Workspace Execution runs your workflow in the cloud. A connection that works in Designer Desktop because your computer is on the same network as the data source might fail in Workspace Execution if the resource is behind your organization’s firewall.
Use Data Bridge to provide a secure tunnel to private network resources that Workspace Execution cannot otherwise reach. Configure a Data Bridge network mapping for each resource that requires this access.
Review these connections for private network dependencies:
Database connections, such as connections to an internally hosted SQL Server.
Email connections that use an internally hosted mail server.
API connections, including Server API tools that access a locally hosted Alteryx Server.
Coordinate with your Alteryx account administrator to configure the required network mappings, then test the workflow in Workspace Execution.
Nota
DCM manages connection settings and credentials. Data Bridge provides network access. Converting a connection to DCM does not, by itself, make a private network resource reachable.
Configure In-Database Connections
In-Database tools can run in Workspace Execution, but they require a file-based connection. Workspace Execution doesn't support adding ODBC Data Source Names (DSNs) to its execution environment.
Create a file-based In-Database connection for the data source.
Update the In-Database tools to use that connection.
Review the tool configurations after replacing the connection.
Run the workflow locally, save it to your Alteryx One workspace, and test it in Workspace Execution.
Before you share the workflow, test it with another intended user. A successful run by the workflow owner does not confirm that other users can access the connection file.
Add Required Drivers and Custom Tools
If a workflow uses an ODBC driver or Alteryx tool that is not included in the Workspace Execution environment, a Workspace Admin must add it through Environment Customization.
Identify custom tools and data source drivers used by the workflow and its macros.
Ask a Workspace Admin to upload the required files through Environment Customization.
Test the workflow in Workspace Execution after the customization is available.
Installing a driver or tool on your computer does not install it in Workspace Execution. Also review older connector tools and replace versions that are unsupported in the execution environment.
Save and Test the Workflow
Run the updated workflow in Designer Desktop and resolve local errors.
Save the workflow locally.
Save the workflow to your Alteryx One workspace.
Run it through Workspace Execution.
Verify data access, generated outputs, email delivery, and API results as applicable.
If other users will run the workflow, test it with those users before relying on it for shared use.
For Analytic Apps, review the Workspace Execution Analytic App support guidance and its limitations before migration. Uploading an app successfully does not confirm that its configuration and execution will work as expected.
Troubleshooting
Non-DCM Connection Error
If saving to Alteryx One reports a non-DCM connection error, review Input Data, Output Data, and Email tools, workflow events, and embedded macros for legacy connections. The DCM Migration Tool might not identify every remaining reference.
If you have converted all connections and the error persists, try these steps:
Use File > Save As to save the updated workflow locally. Preserve a backup before overwriting the existing file.
Run the workflow in Designer Desktop.
Save it again.
Retry saving it to your Alteryx One workspace.
This sequence resolved some persistent save errors during migration testing. If the error continues, record the full error message and the affected tool or connection, and contact Alteryx Support.
Host Unreachable or Connection Timeout
If a connection works locally but fails in Workspace Execution, check whether its target is behind your organization’s firewall. Confirm that the required Data Bridge network mapping is configured for the target resource, then retry the run.
Cannot Access a Network Folder
If a tool references a shared drive or UNC path, move the required files to a supported cloud file store and update the tool configuration. Data Bridge does not currently resolve access to file shares.
Root Element Not Recognized
If you receive a “Root Element Not Recognized” error when saving to your Alteryx One workspace, try running the workflow locally, saving it again, and retrying the save to Alteryx One. This sequence resolved the error in some migration tests. If the error persists, contact Alteryx Support with the full error message.
Missing Driver or Tool
Ask a Workspace Admin to confirm that the required driver or custom tool is available through Environment Customization. Retry the workflow after the required files are available.