Skip to main content

Cloud Execution for Desktop

Schedule and run your Designer Desktop-built workflows in the cloud. Cloud Execution for Desktop lets you link your Alteryx Designer Desktop instance to an Alteryx Analytics Cloud Platform (AACP) workspace and then save your desktop-built workflows to the AACP library (which belongs to your AACP workspace). Once saved to the library, you can navigate to AACP and schedule those workflows to run.

Requirements

To use Cloud Execution for Desktop, you need…

  • Alteryx Analytics Cloud Platform (AACP) Enterprise Version

    • Cloud Execution for Desktop must be enabled on the workspace by an admin. When Cloud Execution for Desktop is enabled on the workspace, two Amazon Web Service EC2 instances of type m5a.4xlarge (16 vCPU, 64GB) are deployed for the purposes of executing your desktop-built workflows in AACP.

    • Private Data Handling is required.

  • Alteryx Designer Desktop Version 2023.1 Patch 1 (or newer)

  • Data Connection Manager (DCM) is required to authenticate an AACP workspace in Designer Desktop.

View, Edit, and Synchronize Alteryx Links

Once you’ve created a link between Designer Desktop and AACP, you can seamlessly connect and synchronize your Designer Desktop with AACP for Cloud Execution on Desktop. This allows you to keep your connection information consistent across both platforms.

Your credentials are available to sync via the Connections section of each link created via Alteryx Links:

  1. Go to File > Manage Connections > Alteryx Links.

  2. Select the Name of the existing link to open and view the details.

  3. To update the link, select the Edit button. Make the necessary edits and select Save or select Cancel to return to the previous screen.

  4. In the Connections section, you select Synchronize to sync your credentials between Designer Desktop and AACP.

    sync-aacp-credentials.png

Once the sync is complete, you receive a confirmation message. If there is an issue with the sync, you receive an error notification.

Save Designer Desktop Workflow to AACP

Follow these steps to save your Designer Desktop workflow to the Alteryx Analytics Cloud Platform:

  1. In Designer Desktop, select File > Save As > Alteryx Analytics Cloud and select your workspace connection, identified by the Data Source Name that you provided when you configured the connection. If you haven’t configured the connection yet, select Add New Link and follow the above instructions.

  2. The current name of your workflow is populated by default in the Workflow Name field. You can customize the name if needed. If your workflow includes any assets, they display below.

    • Check the Group assets by tool* check box to display all of the workflow's assets or file dependencies that are grouped together with the tool they are connected to.

    • Uncheck an asset to omit it from the workflow package.

    *This setting organizes the assets for each tool so that information is easier to parse—it does not change how the YXZP file is created.

  3. Select Save*. At this time, Alteryx validates your workflow to confirm that it doesn’t use prohibited non-DCM data connections. Review the Tool, Connector, and Driver Compatibility section for details. A progress bar indicates the save progress. Once the save is successful, the Save Workflow pop-up appears. Here, you can select to View in Browser (this opens the AACP library where the workflow was saved) or Close to continue working in Designer Desktop.

    *If you’re already authenticated to your AACP workspace, you’re all set. If you’re not authenticated, the save triggers your default browser to open a new window where you can sign in to the AACP workspace that you are saving to.

Important

Cloud Execution for Desktop lets you create and edit workflows on the desktop and execute those in the cloud. Workflows that you build in Designer Desktop need to be edited in Designer Desktop. These workflows are not functional or editable in Designer Cloud at this time.

View Desktop Workflows in AACP

Once saved to AACP, you can find your Desktop workflows in AACP via Library > Designer Desktop. Here you can Download a ZIP file that contains the workflow and any packaged assets, Schedule your workflow to run in AACP, and Delete your Desktop workflows from AACP. Use the three-dot menu associated with the workflow to access these options.

Go to the Library for Assets page for more information.Library for Assets

Open Designer Desktop Workflow from AACP

Follow these steps to open a workflow that was created in Designer Desktop and saved to the Alteryx Analytics Cloud Platform. The workflow opens in Designer Desktop.

  1. In Designer Desktop, select File > Open Workflow* > Alteryx Analytics Cloud and select your workspace connection, identified by the Data Source Name that you provided when you configured the connection. If you haven’t configured the connection yet, select Add New Link and follow the above instructions.

    *You can also access desktop workflows saved to AACP via File > Open Recent.

  2. From the Open Workflow window, select your workflow and then select the Open button. If you have many workflows, use the search box to search for your workflow by name. You can click on the Workflows label to sort the workflows alphabetically in ascending or descending order.

Alternatively, you can download your workflow directly from AACP. To do so…

  1. In AACP, go to Library > Designer Desktop.

  2. Locate your Desktop workflow and use the three-dot menu to select Download.

The download creates a ZIP file that includes the workflow and any packaged assets.

Schedule Designer Desktop Workflow Runs in AACP

Once you save your Designer Desktop workflow to AACP, you can take advantage of Cloud Execution for Desktop and schedule your desktop workflows to run in the cloud environment.

Please note that at this time, Cloud Execution for Desktop allows for 6 concurrent runs of scheduled Desktop workflows per workspace. Any additional runs are queued and will run once one of the 6 concurrent runs finishes.

To schedule your Desktop workflow…

  1. In AACP, navigate to Library and select Designer Desktop in the left panel to navigate to the workflows that you saved from Designer Desktop to AACP. Alternatively, you can add a schedule directly via the Schedules page.Add Schedule Dialog

  2. Select the associated three-dot menu, and select Schedule.

  3. Enter a Name for the schedule.

  4. In the OCCURRENCE section, select your preferred Run type: RecurringOnceCustom, or Event Trigger. Please note that each run type has unique configuration settings. Review the details at the Add Schedule Dialog.Add Schedule Dialog

  5. When you finish the schedule configuration, select Schedule.

Once you schedule your workflow, you can view schedule details and make changes via the Schedules tab of AACP. Here you can…

  • View the schedule status, name, associated asset, and owner.

  • View the schedule frequency, next and last run details, as well as when the schedule was last updated.

  • Additionally, you can edit, enable and disable, and delete the schedule if needed.

Go to the Schedules help page for more information.Schedules

View Cloud Execution Status and Results

Once your Desktop workflow runs as part of your schedule, you can view the schedule results via the Jobs tab in AACP. Navigate to the Jobs tab and select Designer Desktop in the left menu.

Caution

In some cases, Cloud Execution for Desktop workflows might show as Completed on the Jobs page, even if engine errors have occurred. To confirm that the workflow completed without engine errors, please check the job log file.

The Jobs page contains these details (go to the Job History Page for more information):Job History

  • Status: Current status of the job.

  • Job Id: Unique identifier for the job.

  • Asset: The asset associated with the job. In this case, this is the name of your Desktop workflow.

  • Type: The type of job. In this case, this is Cloud Execution for Desktop or CEFD_DESKTOP.

  • Owner: The owner associated with the job.

  • Completed: The date and time the job was completed.

  • Output: If your Desktop workflow produces any output files, they are available here. Select the Output button to download a ZIP file of the associated outputs. The ZIP file contains these items:

    • Engine Log File (regardless of success or failure)

    • All output files associated with the job.

Tool, Connector, and Driver Compatibility

Review this section for important tool, Connector, and driver compatibility notes.

Note

The current Engine version is 2023.2.1.7.

Tool Compatibility

Cloud Execution for Desktop lets you execute workflows (in AACP) with all the tools that are available with the base installation of Alteryx Designer Desktop.

You can also execute workflows that contain these tools:

  • Amazon S3 Download and Amazon S3 Upload Tools

  • Auto Insights Uploader Tool

  • Predictive (R-based) Tools

  • Python Tool*

  • Run Command Tool*

  • Runner Tool*

  • Intelligence Suite Tools*

*Note that some configuration limitations might apply.

Connector Compatibility

The following Connector tools are available with Cloud Execution for Desktop. All data connections must use DCM connections with DSN-less connections (where applicable). Input and output files must be packaged with the workflow.

If you use a Connector tool in your workflow, it must be supported by Alteryx and enabled for use with DCM.

Table 1. Connectors Available with Cloud Execution for Desktop

Connector Tool

Minimum Tool Version

Anaplan Input Tool

V1.1.1

Anaplan Output Tool

V1.1.1

Azure Data Lake Input Tool

V2.4.2

Azure Data Lake Output Tool

V2.4.2

Box Input Tool

V2.5.4

Box Output Tool

V2.5.4

Google Analytics 4 Input Tool

V1.0.1

Google Drive Input Tool

V1.2.1

Google Drive Output Tool

V1.2.1

OneDrive Input Tool

V2.2.1

OneDrive Output Tool

V2.2.1

Outlook 365 Input Tool

V1.2.0

Power BI Output Tool

V3.3.1

ServiceNow Input Tool

V1.1.0

SharePoint Input Tool

V2.4.0

SharePoint Output Tool

V2.4.0

Tableau Output Tool

V1.2.1

UiPath Tool

V1.2.0



ODBC Driver Compatibility

Alteryx only supports drivers that are currently distributed via the Alteryx Licensing portal along with the Alteryx Simba drivers. These are listed below.

Important

The following drivers allow for connections that use the Input Data and Output Data tools or In-DB connections, all of which require DCM credentials and the DSN-less connection option.

Please note that additional restrictions per driver might apply (for example, the allowed authentication method).

Table 2. Drivers Available with Cloud Execution for Desktop

Driver

Minimum Driver Version

Amazon Redshift

V1.5.2.1002

Apache Spark/Databricks

2.6.23.1039

Apache Cassandra

2.7.2.1002

Apache Impala

2.6.14.1016

Google BigQuery

2.4.6.1015

MongoDB

2.3.22.1024

MySQL

1.1.6.1006

PostgreSQL

1.5.2.1002

Snowflake

3.0.0.1001

Teradata

17.20.00.08

Vertica

9.2.0.0003

Microsoft File-Based Drivers: Multiple drivers are loaded automatically on the Windows Container image used for Cloud Execution. While these might work natively, they have not been fully tested yet and are not officially supported at this time.

Microsoft SQL Server: Multiple drivers are loaded automatically on the Windows Container image used for Cloud Execution. While these might work natively, they have not been fully tested yet and are not officially supported at this time.



Notes and Limitations

Access Token Duration

After you link AACP to Designer Desktop, you don't need to sign in to AACP again until either 180 days have elapsed or you have not used Designer Desktop for 30 days.

Schedule-Only Execution

Currently, Cloud Execution for Desktop doesn’t offer an on-demand run option. Once you save your Desktop-built workflow to AACP, you must schedule your workflow in order to run it in AACP.

Workflow Compatibility

Cloud Execution for Desktop lets you create and edit workflows on the desktop and execute those in the cloud. Workflows that you build in Designer Desktop need to be edited in Designer Desktop. These workflows are not functional or editable in Designer Cloud at this time.

Concurrent Runs

Please note that at this time, Cloud Execution for Desktop allows for 6 concurrent runs of scheduled Desktop workflows per workspace. Any additional runs are queued and will run once one of the 6 concurrent runs finishes.

Data Connections

All data connections need to use DCM connections with DSN-less connections (where applicable), as well as input and output files that are packaged with the workflow. If your workflow uses a Connector tool, it needs to be one that is supported by Alteryx and has been enabled for use with DCM.

These types of data connections are not compatible with Cloud Execution for Desktop:

  • Embedded credentials are not allowed in workflows that you save to AACP.

  • Workflows that contain Server data connections are not compatible with Cloud Execution for Desktop.

FIPS

Cloud Execution for Desktop is not FIPS capable.

Inputs and Outputs to and from AACP Datasets

Currently, workflows built with Designer Desktop can’t connect or output to an AACP dataset.

Alteryx Community Gallery Data Connector Tools

Workflows that include Connector tools that aren’t compatible with Cloud Execution for Desktop won’t be able to execute in AACP.

Analytic Apps and Interface Tools

Workflows that contain apps and Interface tools will not allow users to interact with the app in AACP. These workflows technically run in their default state, so if you can schedule the workflow with no interaction from a user, it will execute from AACP. However, if the workflow requires user interaction, the user needs to download the app and run it locally from their Designer Desktop machine in order to interact with Interface tools.

Data Products

Alteryx Data Products (for example, Alteryx Data products from Experian and TomTom) are not compatible with Cloud Execution for Desktop at this time.

Inputs and Outputs with UNC File Paths

Cloud Execution for Desktop uses a service account. At this time, it’s not possible to authenticate a user at runtime to pass Windows Authentication access to the Windows container when executing. This limits functionality for the Directory tool, Input and Output tools, Drive Letter Mappings, and any other tools that require file paths.

At this time, you must either package all files with the workflow when you save it to AACP or the file must be accessed via a supported Connector tool that uses DCM connections.

Run As Functionality

Cloud Execution for Desktop uses a service account. At this time, it’s not possible to authenticate a user at runtime to pass Windows Authentication access to the Windows container when executing.

Run in Safe Mode

At this time, Run in Safe or Semi-safe Mode is not compatible with Cloud Execution for Desktop.

FAQ

Some tools, like Control Containers and Connectors built with the latest Python V2 SDK, require that AMP is enabled in order to use them.

If your workflow doesn't use any AMP-only tools, you can choose to leave AMP disabled. The workflow executes in a Windows container in AACP and runs as it does from your desktop. It uses AMP when enabled and the original Engine for any tools that have not been converted to AMP, or when you leave that AMP box unchecked.

Important

The engine is AMP-enabled in the back end, so if you save an AMP-enabled workflow to AACP, it automatically runs in AMP.

Yes! As long as you properly package the macro with the workflow when you save to AACP. The packaged workflow needs to contain everything it needs to run the logic, including all macros and nested macros, in order to execute properly in AACP. So when you save a workflow from Designer Desktop to AACP, make sure that you package any necessary assets along with it.

Important

If you use CReW Macros or other macro packs downloaded from Alteryx Community, you need to check the box to package those macros in your workflow when you save to AACP. Initially, we only support Alteryx-supported tools, connectors, and drivers as specified above. If you need any other custom or Community Gallery macros in your logic, you need to select them as assets to package with the workflow at the time of the save.