Hi, when using the

@catch

decorator with Argo Workflows, it seems like the generated manifest is missing the

serviceAccountName

property on the

error-msg-capture-hook

this happens using Metaflow version 2.12.23. Without the serviceAccountName property this step is not able to download the workflow artifacts from GCP. I have attached a snippet of the generated manifest. Is this behavior expected?

i believe we need to follow up on this comment - cc @thankful-ambulance-42457

Cool, is there a workaround other than not using the

@catch

decorator?

i dont think this is related to using the

catch

decorator. if you are using the newest version of metaflow, by default

error-msg-capture-hook

isn't enabled

when I run the --help command it says that it is enabled by default

--enable-error-msg-capture / --no-enable-error-msg-capture
                                  Capture stack trace of first failed task in
                                  exit hook.  [default: True]

ah my bad - the heartbeat daemon was disabled. to disable this feature - you can just use

--no-enable-error-msg-capture

while we fix this issue

great thanks appreciate the help