Storyline Files & Dropbox

When using the DropBox client, we are working on our local c drives. These files, in turn, replicate to the cloud. It is disappointing that every other application we use works seamlessly with DropBox but Storyline still requires that we pause syncing every time we want to save a Storyline file.

This started happening to us in the same time frame. Often the only way we can save a file is to pause dropbox syncing first. If you don't, even a File Save As will not work. It partially creates a file with the new name but does not complete the save. The characteristics of the problem are identical to what Abby described above. 

We have the same problem. I hope that you will find a solution to be able to continue as before, because we manage a lot of storyline project and that causes us time wasters.

This exact thing has been happening with my files for months.  I have multiple multiple copies of the same files because it keeps asking me to do this. 

What is the proper way to close a project?  File>Close, then exit the app?? 

I typically save to a network drive.  But we are about to switch protocols to save to our local drive and then copy to network drive.

Can I add my ditto to this thread?  Articulate and Dropbox stopped being friends and it has caused both a hassle and lost work product as I've had folks believe they saved their work only to find that the file was not properly saved.  Something changed in Articulate since it is the only program that is giving me issues.  This should be a high priority issue.

This is still an issue for me.  Is this on the dev team's list to fix soon?

Hello Lauren, this issue persists regardless how, when and where the file is named.  Storyline is notorious about maintaining an ironfist control over the .story files.  For example, if you are working on a project, and simply attempt to copy and paste that file to a separate location, Storyline will not allow it.

It seems to me what is happening is Storyline is trying to maintain control of the file, meanwhile dropbox is trying to sync that file to the cloud.  So when we try to save at any point, storyline gets confused, because another program has interacted with the file to sync.  This triggers Storyline to duplicate the file.  But in making a duplicate, dropbox also tries to sync the new duplicated file, which further confuses storyline. 

Like many dropbox users, our local drives are one in the same with our dropbox directory.  We don't differentiate between what is on the cloud and what is saved locally.

I hope this all makes sense.

I spent well over an hour on the phone with developers at Dropbox trying to figure out a solution to this issue.  In the end, there was nothing that they could do.  The asked if I had to use Articulate or if another product is available because they are unaware of any other products having this type of issue with their service.  Basically, they told me this is a bug in articulate that needs to be addressed.

As Benjamin described very well, this constant control issue of the Storyline file ends up creating versions of a file that are not complete, even when you are renaming new versions and whether you remembered to turn DropBox off before saving, etc. Some of this confusion with files just cost me another 4 hours of work yesterday and the unproductive time dealing with this within a work team is a serious issue. Hopefully, there is something in the works to resolve this.

Yes, I have 2 employees who each lost an entire day's work because of this.  This should be a priority for the Articulate development team.