During a recent project, I explored the Alteryx Server Download a Workflow Package API Endpoint, which includes an optional versionId parameter. The documentation suggests that this parameter should allow users to retrieve specific, prior versions of a workflow package by supplying the appropriate version ID. However, in practice, I found that regardless of which valid prior version ID was provided, the API always returned the current published version of the workflow.
This behavior presented a challenge for our automation use case, where we aimed to implement version control and retrieval solely through Alteryx Server, rather than relying on external tools like Git. After thorough testing and validation, I shared these findings with Zach Hamilton and Marty Moravec at Inspire 2025, who were able to confirm the behavior.
I appreciate the continued enhancements and support the Alteryx team provides for the Server platform and its APIs. Resolving this issue would greatly benefit users who depend on robust version management and automation capabilities within Alteryx Server. Thank you for considering this feedback, and I look forward to future improvements in this area.
