Forum Discussion
Many steps were not saved
I have been observing that if I save a dataflow by clicking the arrow in the Publish button and choosing Publish Later, I lose at least half the steps that I created prior to saving. This happens to larger, more complex dataflows, i.e a DF with 2 tables and 6 steps total won't be affected.
Has anyone else experienced this issue? Is there a right way to save and not publish?
Good question! It could be a timing situation where you lost connection during a particular moment and the draft couldn't be saved and then you published an earlier version of the dataflow. Since there are many scenarios in which this could happen, beyond just the ones previously mentioned, we will address this by giving you a notification on the status of the autosave similarly to how it's done in Microsoft Office apps telling you when the last autosave was made and if there are any issues
10 Replies
Hi ebjim
Thanks for using Fabric Community.
I have reached the internal team for help on this. I will update you once I hear from them.
Appreciate your patience.v-cboorla-msft Thank you!
Do you happen to have a way in which we could replicate this behavior?
