Forum Discussion

RichardNorwood's avatar
RichardNorwood
Community Member
5 months ago

Rise360 - Not saving content - how to prevent data loss

Hi,

We are experiencing an issue with content not being saved while working on Rise. For example, we developed a course on Friday, 21st June, and downloaded the PDF at the end of the day, only to find this morning (Monday June 24th) that the course was back in the state it was on Thursday, 20th June. Fortunately, we have the PDF, but we lost a whole day of work. How can we ensure that this does not happen again, and if it does, how can we retrieve the work and/or identify what has been lost? We don't always download PDFs of our work, so we were lucky this time!

Thanks

  • Hi Richard!

    Sorry to hear that updates to your Rise courses aren't saving properly! I understand how frustrating that must be.

    Unfortunately, since Rise 360 is a web-based program, lost work cannot be retrieved from within the application itself. Are you observing this behavior across all supported browsers, or while using an incognito browser? Also, we advise against keeping Rise 360 open in multiple browser tabs at once. However, if the issue persists among different browsers and clearing the cache doesn't make any improvement, please connect with our team through a support case.

    They'd be happy to continue troubleshooting with you!

  • WallyHobbs's avatar
    WallyHobbs
    Community Member

    I feel your pain, Richard! 😵‍💫 We're currently piloting our first course built in Rise 360 (a two-week course including fifteen or so "courses" built in Rise 360) and we encountered similar issues with Rise 360 not saving our content and formatting changes.

    Sometimes Rise would not save formatting changes like text alignment, or it would miss a minor edit like a trademark symbol or a rephrased sentence, and we learned to painstakingly verify that our changes were being saved, almost edit by edit.

    But at its worst, our writer(s) lost largish swaths of text content edits, which added up to about two weeks of work. From that we learned to keep a text content master in Word and do all our text content revisions in Word--it seems a lot more stable, allows more robust tracking, and also allows more seamless collaboration.

    For context: we're a team of 8 people, and we had 2-3 people collaborating on each Rise "course," using a variety of browsers. Most used Chrome or Edge, or both. We seemed to have the most issues with Rise not saving content in Firefox, although we had issues no matter the browser.

    We appreciate the guidance to clear our caches and limit ourselves to one tab. 🙇‍♂️ But going forward we're using Word for text content. We're currently retrofitting our text content into Word docs by copying-and-pasting from Review 360 into Word, it's tedious and slow but it seems the most efficient of any method we tried (going from Rise > PDF > Word works but requires too much reformatting for our purposes).

    • KellyAuner's avatar
      KellyAuner
      Staff

      Hi Wally,

      Thanks so much for sharing these details with us. I'm sorry to hear your team has been experiencing an issue with losing content and formatting changes. That should be happening!  I've opened a support case on your behalf so we can investigate what's going on, and you'll be hearing from one of our Support Engineers soon via email.

  • WallyHobbs's avatar
    WallyHobbs
    Community Member

    Thank you so much, Kelly! We heard back from the support team a few hours ago and we definitely appreciate the rapid response. They shared tips to avoid the browser back arrow and that issues with saving sometimes happen when authoring too quickly 🤷‍♂️, we were definitely working at deadline speed haha. We do appreciate the guidance and we're learning.

    Still, we've been feeling a lot more secure keeping our text masters in Word, which also offers us other advantages for file storage on our enterprise systems, etc., and we're looking forward to improving our processes when we build with Rise 360 again very soon.