Our team is close to finishing a product (3 hours of work). However, when we apply this last round of edits, the file becomes corrupt. We've gone through 2 iterations of this and at this point see the need to identify the root cause. (to avoid doing another 3 hours of work and having the file get corrupted again)
Potential Root Causes:
File size (close to 170 KB) , which seems relatively large. Is this large enough to trigger a corrupt file?
Some specific object within the file that is corrupt. (no clue how to efficiently identify)
We identified an object with an attached video in the file that we couldn’t delete without automatically deleting all slides after that point in the file
Any insights on typical root causes and how to solve would be much appreciated.
Thank you for reaching out, and I'm sorry to hear you're experiencing issues with your project!
Is your team working from a local hard drive? We don't recommend working with files on a network drive as it can cause erratic behavior. If it's a local drive, but also syncing with a service such as OneDrive or Dropbox, it can cause a similar effect as a network drive.
1 Reply
Hi, David.
Thank you for reaching out, and I'm sorry to hear you're experiencing issues with your project!
Is your team working from a local hard drive? We don't recommend working with files on a network drive as it can cause erratic behavior. If it's a local drive, but also syncing with a service such as OneDrive or Dropbox, it can cause a similar effect as a network drive.
If this is not your scenario, can you share the .story file with our support team through a case? We'll delete it once we're done troubleshooting!