Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.
Hi Steve,
Thank you for bringing this to our attention. We've yet to implement some features that would help you get around this current issue in the beta.
In the meantime, you should be able to get around this issue by saving the current dataflow to a new instance, and then continuing your work in the new instance:
![]()