Data Connections, Credentials, and Connectivity
Connection management
Alteryx Server centralizes data access through data connections managed by Curators. A connection stores the driver/connection string and credentials so workflows reference the connection rather than embedding secrets. Connections can be system connections (available to all) or scoped to users/groups. Know that connection types include database, file, and cloud connectors, and that the worker (not the Gallery) must be able to reach the data source.
Credentials
Credentials are stored in the credential store, encrypted, and referenced by connections or workflows. Understand the difference between embedded credentials (stored with the connection) and user-run credentials (the schedule owner's credentials are used at run time). OAuth-based cloud connections require token refresh configuration.
Connectivity traps
A frequent trap: the Gallery can reach a data source but the worker cannot - connectivity is required on the worker host, and firewalls/network rules often differ. Another trap: assuming a connection that works interactively will work on a schedule - scheduled runs use the schedule owner's credential context, which may lack access. Also watch for driver version mismatches between designer and server.
Worked example
A scheduled workflow fails with a connection error, but it runs fine in Designer. Check: does the worker host have network access to the source? Does the schedule owner have permission on the data connection? Is the driver installed on the worker? Any of these explains the gap between interactive success and scheduled failure.
Rule of thumb
Connections live on the server, but connectivity must exist on the worker. Always test scheduled runs in the schedule owner's credential context.