Thanks for reaching out! We recommend working locally on your desktop or C drive, as working from a network shared drive or the cloud can cause file corruption or prevent you from saving changes.
You can place a copy of your project on a network drive or a USB drive for backup purposes, but avoid reopening the file until you've moved it back to your local hard drive. This article below shares more details on that!
Yes, I am having continuous problems with crashing. I use One Drive with regular syncing to the Cloud. I'm confused if files with the green check are truly local (which according to Microsoft are available on the local computer), but does this meet the Articulate definition of "local"? Thank you!
If your folder automatically syncs with OneDrive, it could cause the same issues as working on a network drive, so we usually recommend disabling the auto-sync to avoid erratic behavior.
I have to store all the files on onedrive because of the volume of modules I create, so I move them back to my C drive when I need to edit them. Lately, though, when I try to publish, the wheel just spins for hours and I can't publish anything. Given that so many businesses are moving to one drive, is there any consideration for making Articulate function with that? I'm at a loss right now because I can't even publish anything and I'm worried about how I can find a working solution now that Articulate doesn't even work on my C drive.
Sorry to hear that you ran into this behavior. Working out of your C: drive shouldn't be causing the issues you described. Can I ask if the behavior you're experiencing is happening to all of your project files or just a few? If all files are affected, I recommend repairing Storyline 360.
If only a few projects are affected, please share copies of your project file here or in private by opening a support case so we can take a closer look at what's causing publishing to fail. We'll delete it when we're done testing!
5 Replies
Hi Beth,
Thanks for reaching out! We recommend working locally on your desktop or C drive, as working from a network shared drive or the cloud can cause file corruption or prevent you from saving changes.
You can place a copy of your project on a network drive or a USB drive for backup purposes, but avoid reopening the file until you've moved it back to your local hard drive. This article below shares more details on that!
Yes, I am having continuous problems with crashing. I use One Drive with regular syncing to the Cloud. I'm confused if files with the green check are truly local (which according to Microsoft are available on the local computer), but does this meet the Articulate definition of "local"? Thank you!
Hi, Stephanie.
If your folder automatically syncs with OneDrive, it could cause the same issues as working on a network drive, so we usually recommend disabling the auto-sync to avoid erratic behavior.
Let me know if you have additional questions!
I have to store all the files on onedrive because of the volume of modules I create, so I move them back to my C drive when I need to edit them. Lately, though, when I try to publish, the wheel just spins for hours and I can't publish anything. Given that so many businesses are moving to one drive, is there any consideration for making Articulate function with that? I'm at a loss right now because I can't even publish anything and I'm worried about how I can find a working solution now that Articulate doesn't even work on my C drive.
Hi Valeri,
Sorry to hear that you ran into this behavior. Working out of your C: drive shouldn't be causing the issues you described. Can I ask if the behavior you're experiencing is happening to all of your project files or just a few? If all files are affected, I recommend repairing Storyline 360.
If only a few projects are affected, please share copies of your project file here or in private by opening a support case so we can take a closer look at what's causing publishing to fail. We'll delete it when we're done testing!