Forum Discussion

Payal0810's avatar
Payal0810
Community Member
5 months ago

Issue with Storyline File – Triggers Misplaced and Progress Not Saved

Dear Articulate Support Team,

I’m reaching out to report an issue I’ve encountered with a Storyline file that appears to be affecting trigger functionality and progress saving.

On Friday, I saved the file and published a Review 360 link. The file was not accessed over the weekend. However, when I opened it again on Tuesday, I noticed that several triggers were misplaced, and the progress made was not reflected—despite no changes being made to the file during that period.

Additionally, even after incorporating feedback and saving the file the following day, the updated progress still does not appear in the published version. This has happened multiple I kept reworking on slides because of this issue.

Key Details:

  • File Type: Storyline (.story)
  • Issue: Misplaced triggers and unsaved progress
  • Timeline:
    • Friday: File saved and review link published
    • Tuesday: File accessed again; issues observed
  • No access or edits were made between Friday and Tuesday
  • Browser cache cleared and file republished, but issue persists

Could you please investigate this and advise on any known issues or recommended steps to resolve it? 

Thank you for your support.

storyline 360

1 Reply

  • LaurenDuvall's avatar
    LaurenDuvall
    Staff
    5 months ago

    Hi Payal0810! Thanks for reaching out. I'm glad to help.

    It sounds like you made updates to your Storyline 360 file and published it to Review 360, but when you came back later, things looked off—some triggers were out of place, and your progress wasn’t there. That’s definitely frustrating, and I’m here to help figure it out.

    Just a quick note: Review 360 won’t reflect changes unless you republish your course from Storyline 360.

    And your file shouldn’t change unless you do. If it is, double-check that you're saving and working from your local drive (like your desktop). Shared or network drives can cause all sorts of strange issues.

    If you're already working locally and still seeing problems, we’d love to take a closer look. You can attach your file here or send it to us privately in a support case. Whatever works best for you.