The only scheduled run that seems to run was the p...
# ask-metaflowa
adventurous-gigabyte-81428
04/03/2024, 2:03 AMThe only scheduled run that seems to run was the production version. Is this by design, or i've miss some steps. Any guidance will be helpful ?
✅ 1
adventurous-gigabyte-81428
04/03/2024, 5:16 AMFound the answer, turns out the concatenated workflow name exceed 52 characters . Digging into the argoworkflow logs
Copy code
level=error msg="cron workflow name \"deploymentinfoflow.user.samuel.than.deploymentinfoflow\" must not be more than 52 characters long (currently 54)" conditionType=SpecError namespace=cia-team-ai workflow=deploymentinfoflow.user.samuel.than.deploymentinfoflowadventurous-gigabyte-81428
04/03/2024, 5:17 AMSeems like there is no good way to tell just by looking at the Argoworkflow UI itself, and there is an existing issue filed at https://github.com/argoproj/argo-workflows/issues/6781
s
square-wire-39606
04/03/2024, 12:01 PMYes it’s been an issue that has bitten us in the past - a good reminder to find a fix within metaflow code base rather than relying on argo to ship a fix