Hello! I have recently started using Metaflow and noticed that code snapshots are not being saved to my S3 datastore when I deploy the Flow locally with

argo-workflows create

. I do have access to the S3 datastore from my local machine, so i’m not sure what may be happening with Metaflow. Does anyone have any suggestions for what might be happening?

@witty-jackal-1438 what is the output of

argo-workflows create --only-json

for your flow?

Hi @square-wire-39606, I apologize for the delay here. That command generates a large amount of json text that looks like the Argo workflow template

can you paste that output or alternatively what makes you believe that the code snapshots are not being saved as expected?

Here is the output. I have checked that bucket and I am seeing the code snapshot saved in the

data/00/

folder, but when i run the workflow on Argo I seem to be missing a step. The start(0) step is missing when i deploy locally, but if i create the workflow from our gitlab CICD runners, the workflow includes the start(0) step

what is

start(0)

?

Here is an screenshot of a workflow created from a CICD deploy script

this could be because of different argo versions

Is there a recommended Argo version for using Metaflow?

we support a very wide range - it seems that your local deployment is also working - the argo UI is just a bit different

It seems that was just leading me down the wrong path, i did some more testing and was able to verify that code snapshots are working. Thanks for the help clarifying things!