Forum Discussion
Many steps were not saved
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
We believe that we've determined the issue and we're working on a way to address it.
The issue is related to how frequently and how successfully the draft of a particular dataflow is being saved. This means that in some cases the user actions might be a bit too fast for the Dataflow service to catch up before publishing.
Good to know that a fix is on its way, but it would be good to know: how fast is too fast?
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