Layer box covered in big red cross?

Uh-oh Hannah! There are a few things you can try before you start from scratch. We want to avoid that if possible!

First, are you working from your local C: drive, and not a network or flash drive? 

If so, are you able to save and close the project? From there, import the project into a brand new Storyline file. 

Let me know if that solves it!

Hey Hannah,

Sorry that's happening, definitely not what I'd expect to see!

I have a couple suggestions to start out here:

1. Make sure that you're saving all your files to your local computer (C:Drive or Desktop) and not a network or shared drive.
2. Open a brand new file, and see if the same thing happens in that one. 
3. If the issue is specific to one file and you don't see it happen in a new one, import your slides from the problem file into a brand new file and try working from the new one.

Let me know how that goes! 

Same thing just happened for me. This happened after using one of the timelines from content library (not sure if that is a causal relationship). I can't fix this and have a deadline today. Tried importing into a brand new file. Two weeks work - do I need to start from scratch?

After closing and re-opening a few times, the error has corrected itself.

So glad to hear it's working again, Dorothy! To ensure it doesn't happen again in the future, you'll want to follow these best practices. 

Hello - the same thing has happened to me, after copying and pasting text from one screen to the other.  Really disappointing experience with Articulate 360...and it's slow.  Working from C drive on a brand new laptop.

Hello Shiraz,

Sorry to hear that you're experiencing difficulty with your course and with some general slowness.

Are you utilizing the latest update to Storyline 360, which is Update 13. You can find all of the details and the directions to update here.

If you were already up-to-date, I would recommend that you conduct a repair of your software. 

If that does not correct the issues that you are seeing, I'd recommend reaching out to our team directly here.

This was not working for me :(

Hi Carla, sorry you're having trouble!

Try doing a repair on Storyline – that should sort everything out. Follow the steps linked below for your version: 

• Storyline 360 Repair
• Storyline 3 Repair
• Storyline 2 Repair

Hi - I'm having the same issue.  Tried opening and closing the file and the software several times.  Still happening.  

Hi David,

Thanks for reaching out and letting us know that you are running into a similar issue with your project. 

I see that you've reached out to our support team as well and Chino is already assisting you.

The Big Red Box is back.  I thought this was resolved in a previous version? We are on the latest version and it is still occurring.

Sorry to hear the red X is back, Theresa!

It's typically a sign of corruption in the file, where these tips help mitigate the risk. Let's tackle the next steps together:

1. I would first try to import the slides into a new Storyline project.
2. If that doesn't help, let's try a simple repair. 

If those two steps don't help, our Support team is ready to jump in to explore further. Please keep us posted!

Hi,

I also had the same issue after importing a slide from content library into my working file. While editing one layer, I started getting this error. I think it's related to the import from content library. I closed all instances and restarted the program. A few minutes later, it is happening again. Any suggestions?

Thanks
Ismail

Hi Ismail,

Katie covered some excellent first steps in her post above!

If you've reviewed them and are still finding yourself running into issues, feel free to connect with a support engineer so we can dig a bit further into figuring why this is happening.

• Submit a case here!
  

Hi Ren,

Thanks for responding to this. I managed to recover my file by exiting articulate, updating to a newer release and restarting my computer. I'm not sure if it was a RAM issue or the import of slide that caused this error. I saved it as a new file and happy it didn't show again after restart.

Hi Ismail,

Sweet! Glad to hear updating the software and saving it as a new file helped with the error you were seeing!