For example, let's say I have a flow that has a published version 1.0:
And a checked-out 2.0 version that is locked by my user:
If I use Archy and Client Credentials to export the latest flow:
The exported file name says it is version 1.0, which has the contents of version 2.0!
However, if I use a token of my user (the one that has the flow locked):
Then the exported file name has the name according to its contents:
------------------------------
Adrián Santamaría
------------------------------
Original Message:
Sent: 02-23-2026 11:55
From: Adrián Santamaría
Subject: Bug when exporting flows that are checked out by other user
Hello
I think I've discovered a bug in Archy when using the export command to export a flow that is currently being edited.
When specifying the version latest, if the credentials are not the same as the user's that has the flow locked, when downloading the flow, the result file has a wrong version in the name.
For example, let's suppose this scenario:
- Flow published version: 10.0
- Flow checked-out version (being edited): 11.0
- User who has the flow locked:
UserA
We have 2 cases:
Case A (correct behaviour):
archy export --exportType yaml --flowId the-flow-id --flowVersion latest --authToken token-of-userA:- Exported file:
Example_flow_v11-0.yaml - Contents of the file: Version being edited (11.0)
Case B (wrong behaviour):
archy export --exportType yaml --flowId the-flow-id --flowVersion latest --authToken token-of-userB: <- Other user's token (or client credentials)!- Exported file:
Example_flow_v10-0.yaml <- Wrong version! - Contents of the file: Version being edited (11.0)
Note that in Case B, specifying --flowVersion latest vs --flowVersion 10.0 would result in files with the same name but with different contents!
#Archy
------------------------------
Adrián Santamaría
------------------------------