Flyte enables production-grade orchestration for machine learning workflows and data processing created to accelerate local workflows to production.

Flyte

Could it be that gate notes cannot be unblocked in conditionals? Video in the thread :thread:

61712112-10F3-486D-AE10-19E3F71C0551.mov

Another nit, I’ve tried to use `approve` first in the conditional, but resorted to using `wait_for_input` as the first would lead to
```tError 0: Code: VariableNameNotFound, Node Id: n1-n1, Description: Variable [o0] not found on node [n1-n1]```

can you copy here the code that produced that error?

Sure, I’ve put it into <https://gist.github.com/bstadlbauer/d83cff2f84b34e46b0291fa7666881a0|this gist>. The example is slightly different then the video, but I’ve also tested it and it fails in the same way.

This is with:
• “<http://ghcr.io/flyteorg/flyteconsole-release:v1.5.0|ghcr.io/flyteorg/flyteconsole-release:v1.5.0>”
• “<http://ghcr.io/flyteorg/flytepropeller:v1.1.66|ghcr.io/flyteorg/flytepropeller:v1.1.66>"
• The rest of the components is on 1.3.0


Our current workaround is putting the `wait_for_input` in a sub-launchplan as that will show as a separate execution where the resuming works.

cc <@U0231BEP02E>

Ah, actually I think this is due to a bug we had in `1.5` around gate nodes - this should be fixed in <https://github.com/flyteorg/flyteconsole/releases/tag/v1.6.2>

<@U0231BEP02E> Thanks for the quick response! I’ve tried 1.6.2 but it seems like the issue still persists

Ah, okay then let me take a look into this.