Project won't save - Storyline 2

Hi Max,

The forums have an upload limit, so you may not be able to share it here - but you should be able to upload here on our Support site.  Since you mentioned it's also happening on more than one .story file, have you also already gone through the repair steps? 

Hi Max,

Thanks for confirming you already did the repair. What browser are you using to try to upload to the support site? I haven't heard of any issues today - so I'd recommend trying from a different browser and ensuring that there aren't any security settings that would prevent you from uploading information. Also, you can proceed with the case without sharing the screenshot right away and once the case is opened our team will be able to connect with you and share a link where you could upload the files directly. 

Oh, also - when you reply via email it includes your signature as a part of the reply. You can edit your post if you'd like to remove that information. 

Hi Max,

Do you  have one of the case numbers handy so that I can take a look? If you submitted two, they likely were combined on our end so either number should work. I know our Storyline team has been playing some catch up following the holiday last week, so I just want to check in on the status. 

You mentioned that on or around slide 20 is when the issue started to occur in a new project, were you able to remove whatever element you had added to that slide and see if the you could continue to work normally? I'm wondering if it's a specific item you're including that could be contributing to the error. Also, I know you've done the repair, and I believe you said you did the full repair detailed here but I also wanted to confirm that you're working locally as mentioned here. 

same problem here. was able to save just fine over the last 30 days I've been working on this file but now i'm not able to. Not interested in uploading yet another file to fix. This build seem extremely unstable. Not very pleased.

Hi Max,

Thanks for the case number, I was able to track it down and escalated it since our team is having a bit of a backlog after the holiday last week - so you should be hearing from someone soon. I'll continue to follow along as well. 

Hi Adam,

I'm sorry to hear that you've run into the issue as well, and our team is actively looking into this and working on a fix. The best course of action right now is to connect with our Support team here so that we can see your file, the exact error message you're receiving (there are a few different ones in this thread now) and pull some system information to help our QA team as they continue to try to reproduce the issue and track the error. 

Hello Ashley,

Not to seem presumptuous or to state the obvious, but have all these particular case #'s been identified/grouped together for analysis? I have not heard anything about my case (00438551) since the 20th, nor has my co-worker heard anything about a 'mirror' case # (004437091) since the 14th. This seems to be a significant issue but besides you Ashley (and a few other Articulate staffers on this thread), I'm not seeing or hearing any updates much less progress towards resolution.

Hi Michael,

Yes, we've shared all the case numbers and project files with our QA team. As I mentioned earlier, there are a few different error messages and set ups that we're seeing - so it's difficult right now to say that they're all the same - but they are being investigated together. I do see that your case was shared with our QA team, and until we have additional information to share our support engineers would not reach out again on your case unless you emailed them with updates. As for the other case number you shared, I don't see a case associated with that one and it looks to be at least one number too long. Can you check that again or if you can share the co-workers name I can try to track it down that way? 

There are a few of us who moderator the forums (myself included) to reply, assist with troubleshooting and provide updates. Our QA and Engineering teams don't often have time to get into the forums to reply, so there may only be a handful of us that you hear from here. Please know that we're in communication with them regularly and sharing updates as they occur in this thread or from our support engineers who are testing files in the case. 

Thanks Michael - I see it now, and see it's connected to the issue mentioned so once there is additional information you'll both receive notification about it through your case and if you're subscribed to this thread.