Review 360 - Localization Tool Freezing
We have not had any issues in the past month using the Review 360 for translation validation, but all of a sudden yesterday or reviewer is running into issues when validating the text. He informed me the site freezes and he has to close out of everything, then go back in with hopes of the reviewed text has been saved. Has anyone experienced this issue?Can't see previous comments in the new version published to Review 360
I cannot work out why I cannot see the previous feedback provided on the same course that has been published to Review 360. I have rolled back to each version (1-4), but cannot see any comments. I have checked the ellipses to ensure all comments, including resolved ones, are visible, but still no record of stakeholder feedback. How do I fix this?Problem with viewing Author's avatar
Dear all, have any of you had ever a problem with the author's avatar image similar to this? I already deactivate and activated again the avatar, changed the avatar profile picture, but still does not work :( I still can see it when I am working on Rise 360, but I cannot see it on Review. Have any of you experienced similar situation? Thank you so much in advance!RISE Review 360
Hello, when reviewers leave comments and another replies with the mention @, is there anyway when a reviewer clicks on the email it goes right to their comments? Or do they have to scroll the whole feedback comment section ... I think I saw they can sort by "recent", but any other way at this time? If not, would be good to consider. My reviewers sometimes have an issue.Copy of a localized (multi language) file cannot be published to a NEW review name
HELP! I created a file and localized it with English/Spanish. I published for review. It went great. Now I need to make a similar file, so I started with my existing file and made a copy of it. Made a whole bunch of changes, updated translations, etc. But when I go to publish to review 360, it wants to publish to the original review. But this is a NEW file. How do I fix this? Do I have to start over every time with a non-localized file and redo all the formatting (getting rid of scroll bars, etc) again? I should always be able to publish as a NEW review when I want to. Please advise.Storyline Update Issue: Screen Recordings Play from Slide Start Instead of Timeline Position
I’m running into a significant issue after updating Articulate Storyline 360, and I wanted to see if anyone else has experienced this behavior or found a reliable workaround. We have multiple Storyline projects that use screen recordings in View Mode. In the previous version of Storyline, the screen recording playback followed the placement of the recording on the slide timeline. For example, if the screen recording was positioned to begin at a certain point in the timeline, it would play from that timeline position as expected. After updating Storyline, these same slides now appear to automatically start the screen recording from the beginning of the slide, regardless of where the recording is positioned on the timeline. This has caused our audio, captions, and screen actions to become out of sync. This is not just happening in timeline preview. The issue is also present in the published output, which makes it much more concerning. I have already submitted this issue to Articulate Support, and they were able to replicate the behavior. It has been logged as a possible software bug. The current workaround provided was to roll back to Storyline 360 Update 117. At this point, I’m trying to determine the fastest and most reliable way to resolve the issue without simply waiting for a future software update. We are preparing to publish approximately 20 Storyline projects into one LMS course for about 6,000 students, so rebuilding every affected slide manually would be a major lift. Has anyone found a practical workaround for this? Specifically, I’m trying to determine: Can the screen recording be prevented from automatically playing at the start of the slide? Is there a way to start or control the screen recording with a trigger instead of relying on the timeline? Is there a fast way to recreate the original timing behavior from the previous version of Storyline? Has anyone had success replacing the screen recording object with a video file, trimming it, or using layers/triggers to replicate the original timing? Is rolling back to Update 117 currently the only reliable option for projects that depend heavily on timeline-based screen recordings? Any insight would be greatly appreciated 😃, especially from anyone who has already had to fix published projects affected by this issue. I’m trying to identify the least risky and fastest path forward while preserving the original timing, audio sync, captions, and learner interactions.Storyline issue – Layer not persisting during review since recent updates
Hello everyone, I’m encountering an issue in Storyline that seems to have appeared after the most recent updates. Context: I’m using a question slide with: one Correct layer one Incorrect layer I added a third layer called “Lock”, designed to hide the Next button. Main slide: Standard question slide Next button visible after answering Correct / Incorrect layers: Display feedback Next button available to proceed Triggers in Correct / Incorrect layers: Lock layer: Hides the Next button Trigger logic: The “Lock” layer is triggered when the learner clicks the “Next” button Its purpose is to prevent navigation when the slide is revisited This is mainly used during review mode via a lightbox (recap) Expected behavior: When the learner revisits the slide in lightbox/review mode, the “Lock” layer should remain active, ensuring that the Next button stays hidden. Current behavior: The “Lock” layer does not persist upon revisit The slide returns to its base state with the feedback The Next button becomes visible and clickable again This breaks the intended restriction logic during recap Additional info: This setup worked correctly prior to the recent updates Question: Has anyone experienced similar behavior with layer persistence or slide state reset in lightbox/review mode? Could this be linked to a recent change in how Storyline handles layer states or slide revisits? Thanks in advance for your help!
