For processes in a Displayr document that save a file to the Displayr cloud drive (eg: stacking data, publish > export data) the saved file will overwrite any file in the Cloud Drive by the same name. This caused an issue for a user who was referencing a stacked file from their cloud drive, then later tried to download publish the same stacked file (this overwrote the stacked file and caused many variables to error).

The feature request is that the user is at least alerted if the file creation will overwrite an existing file.

Overwriting a file, however, is a virtue for some automated processes, so I imagine that, if there is an automation that requires a file to be saved out (eg: if updated data gets automatically stacked) and overwrite an existing file, then this should still be possible.

Workaround: Not really. Other than the user could be more careful.