Pinned Reply
Hello Everyone! ✨
I'm happy to share that we have released a new update for Storyline 360 (Build 3.74.30180.0)
In this update, we have implemented a fix for:
- Storyline 360 crashing when adding conditions to triggers or publishing to Word.
As a first step, I recommend updating Storyline 360 to the latest version. Here's how:
If you have any questions, please let us know in this thread or privately in a support case.
Have a great day!
53 Replies
Hi there, Clint. So sorry you're running in this!
This is an excellent opportunity for our Support Engineers to jump in and help. I reached out to the team, where they'll be in touch with you on the next steps by email shortly!
..and since you have Articulate 360 for Teams, you'll get priority support!
Wonderful. Thank you for your assistance.
Saaaame! This issue happened to me on both version 3.33.20697.0 and the newest version 3.3420804.0) I have done all the same trouble shooting options that I could think of.
Hi Annarose,
Sorry you're running into this is as well, and I appreciate you opening a case with our support team! It looks like Ronaziel has replied with some next steps to try before proceeding further.
Keep at it with her, and I'll follow along as the case progresses to see what the root cause of this issue is!
Currently, my team is working on windows updates to see if that fixes things. As a TEMPORARY fix, you can turn off the new trigger wizard in the options, and I can make conditional triggers using the old interface.
Clint, thank you for providing an update on your work around. That fixed the issue with the conditions! I'm going to relay this info to my team.
Ren, thank you for following up, I'll continue to work with Ronaziel to see if this can get fixed.
I've been getting these crashes too - when adding conditions to triggers. I will see if switching to the old interface for triggers fixes the problem, as suggested by Clint.
Thanks, Aaron. Be sure to let us know the results of your testing. It looks like a few folks were behind on Windows updates and that allowed the software to work correctly as well.
You are welcome to work directly with our support team here if needed.
Thanks Leslie - just confirming that I'm not experiencing any crashes since turning off the new triggers functionality (and I've been doing A LOT of work with conditional triggers the last couple of days).
I should just say that I really like the new triggers interface - more intuitive, and the ability to turn triggers off without deleting them is great for testing purposes. Hoping I can safely turn this new feature back on soon!
Thanks for sharing, Aaron.
A quick update from me - I installed the May 5, 2020 updates to the Articulate Desktop App and Storyline 360, then tried turning on the new triggers feature again. No crashes so far, even though I have used a lot of triggers with conditions. Looks like this fixed the issue for me!
Thanks Leslie.
As a final follow up, this appears to be an issue with older versions of Windows 10. Once my team installed the latest updates, the trigger wizard worked fine.
Thanks so much for popping back in with an update, Clint.
This post was removed by the author
Hmmm... This crashing when trying to add a condition happened to me a couple of months ago, and it's doing it again now, repeatedly.
I've reinstalled SL 360 and have the latest version of Windows 10.
Are there any options for correcting this other than turning off the (superb) new interface?
Hi Allan,
I am sorry to hear that this issue is resurfacing on you. A couple of questions for you on this:
Please keep us posted and let us know if you have any questions!
Hello, Vincent. I'm sorry for the delay in responding to this!
SL 360 is v3.40.22208.0, and I'm using Windows version 1909.
I haven't seen any recurrences of this since I wrote about it here, but it has come up now and then in the past.
Thanks.
Hi Allan,
I'm glad to hear that the crashing stopped, and appreciate you circling back!
We want to understand the connection between the new trigger panel and crash, where our Support Engineers can jump in at any time. If this happens again, please let us know:
Just FYI this is still an ongoing issue and I just updated to the most recent version again today. I will try turning off the new trigger Wizard and see if that still works for now. Seems like this is taking years to address!
Oh dear, didn't realize the classic trigger workflow was retired Jan 2021. So what do we do now when it instantly crashes every time I try to add the conditions to my trigger?
Hello Ambre!
Sorry, this is affecting your workflow! I see that you've submitted a support case and are working with my teammate, Cleo! You're in great hands.
For anyone who is running into this issue, here's what Cleo suggested:
To initially troubleshoot the issue, first repair Storyline 360.
Once installed and updated, try to open your project file, then test it. See if you can still replicate the issue.
If you continue to experience the same crash, try to do the following to get rid of minor corruptions:
1) Create a new project file and save it on your local drive C:
2) Set the Design > Story Size, with the same dimension as your old project.
3) Select Slides > Import > Import Storyline. Find your old project file and import all the slides.
4) Save your project and see if you will encounter the same issue.
If you have additional questions, you can reach us in this discussion or in a support case.
Are there any new updates to this issue. I have tried every option described above; repair, uninstall, yet the crash still occurs when attempting to add a condition to a trigger to an existing file, or even a brand new file with one slide.
Win 10 1909 - 18363.1500 build
Hello Chuck!
I'm sorry you're also running into this issue! I see that you're working with my teammate, Ronaziel, in a support case, and Ronaziel just replied to your initial request. We'll continue the conversation via email.
Hi
I just updated my Storyline 360: v3.52.2524.0 and I am having the same problems. When I am trying to add Conditions to a trigger the program pop up and error message and shots down. Also when I try whit in a new project.
Windows 10 Enterprise vers.: 10.0.18363 Build 18363
Join the legion of users who are having the exact same problem, but apparently only on their computers, because Articulate insists it is incapable of reproducing the problem on their end:
https://community.articulate.com/discussions/articulate-storyline/trigger-bug-in-storyline
https://community.articulate.com/discussions/articulate-storyline/object-conditions
BTW, uninstalling/reinstalling is not a "solution," partly because Articulate does a significantly less-than-adequate job of removing all of its entries polluting the system registry, and partly because it is an admission that they really don't have a firm grip on the root cause.