I'm encountering an issue when trying to acquire Resources that are created using code.
Attached is a minimal example that shows the issue. The flow contains a Resource asset defined on a Group, and at the beginning of the flow I add an Operator to this Group using a code stage. The token will move through the subsequent Acquire Resource activity without complaining, but the token label that should point to the Operator shows <no path>.
Can this be solved?
Background
In my use case, the number of Operators, Transporters, etc. are parameters, so creating them dynamically using code seems to me like the best way. But maybe there is a better way altogether of achieving this?
