Not sure if it's a bug, but I have a observation to report. We've been trying to figure out why our Metflow generated Argo workflow doesn't kick of at a specific time automatically. Turns out if we remove the @project decorator it works. Is this a known behavior?

interesting. if this is the case, then definitely a bug. looking...

Probably it is worth looking at the workflow-controller logs in Argo. The one time (outside of the context of Metaflow) I have seen this type of behaviour in Argo it was due to the

CronWorkflow

exceeding the character limit on the

name

field. The

CronWorkflow

was deployed to the cluster, but when it came to triggering it failed due to the character limit.

Great point!

If it is the issue it will show up in the controller logs

I think it's likely that this length thing is the issue.