Notes, Limitations, and FAQ
Notes and Limitations
Review this important information about Cloud Execution for Desktop.
Access Token Duration
After you link AAC to Designer Desktop, you don't need to sign in to AAC again until either 180 days have elapsed or you have not used Designer Desktop for 30 days.
Schedule-Only Execution (Workflows)
Currently, Cloud Execution for Desktop doesn’t offer an on-demand run option for workflows. Once you save your Desktop-built workflow to AAC, you must schedule it to run in AAC. Desktop Analytic Apps can be run on demand in AAC.
Workflow Compatibility
Cloud Execution for Desktop lets you create and edit workflows on the desktop and execute them in the cloud. Workflows that you build in Designer Desktop need to be edited in Designer Desktop. At this time, these workflows are not functional or editable in Designer Cloud.
Workflow Size
The total size of your workflow cannot exceed 200 MB in order to save to AAC.
Temporary Files
Cloud Execution doesn't support writing to a temporary directory (%temp%filename.ext). Output files saved to a temporary directory are not included in the final zipped output for Cloud Execution jobs (including Analytic Apps).
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 packaged with the workflow. If your workflow uses a Connector tool, it needs to be one supported by Alteryx and 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 AAC.
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 AAC Datasets
Currently, workflows built with Designer Desktop can’t connect or output to an AAC 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 AAC.
Analytic Apps and Interface Tools
You can now run your Designer Desktop-built Analytic Apps in the cloud. Once saved to the library, you can navigate to AAC and run your apps via the UI (which utilizes the power of App Builder to help render the app in AAC).
Many Designer Desktop Interface tools and elements are compatible with Cloud Execution for Desktop. For details, go to Run Analytic Apps in AAC.
Chained Apps
Chained apps are not supported via Cloud Execution for Desktop.
Data Products
Alteryx Data Products (for example, Experian and TomTom Alteryx Data products) are not currently compatible with Cloud Execution for Desktop.
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 them to AAC or access the file 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 AAC 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 AAC, it automatically runs in AMP.
Yes! As long as you properly package the macro with the workflow when you save to AAC. The packaged workflow needs to contain everything it needs to run the logic, including all macros and nested macros, to execute properly in AAC. So, when you save a workflow from Designer Desktop to AAC, 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 AAC. 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.