"Pause timeline on This Layer" pauses the timeline on every layer.

Argh. It's a pretty major bug, isn't it? Just encountered it today and I can't implement a workaround. So frustrating.

This issue has been with the QA team for a year now, and people are still encountering it. Pretty slack.

Hi Gary and Diarmaid,

I do see that our QA team has this bug and has been doing some testing but no official fix yet. It seems that a potential workaround is to trigger the pause of the timeline using a button vs. based on the slide's timeline. 

Once we have additional information to share we'll report back here. 

Hi,

Has this issue been looked into yet?

Thanks.

Hi Gary,

I don't have any status updates to share, but it has been sent along to our team for them to investigate further. Once we have any additional information we'll share information here with the folks subscribed in this forum but we're unable to offer a timeline. 

I've encountered this bug again recently whilst building a course. In the one year and three months that this bug has been with your QA team (you do know QA stands for Quality Assurance, surely these issues should be passed on to your development team?), has anything been done to address the issue?

Hi Gary,

I do see that this issue has been reviewed by our team and they've tested some fixes, but I don't have any additional information to share in regards to a timeframe when that would be completed or if there would be an update. I would advise to continue using the workaround of using a button to pause the timeline. 

Is there any news on this bug yet?

This is a significant problem and I can't believe nothing's been done about it after coming up to TWO YEARS. Along with a similar bug in HTML5 that I logged and also haven't heard anything about yet...see here...this is getting beyond a joke.

For me, there's literally no point in using entrance/exit animations or animations in general on objects in layers as they need to pause and resume properly.

I can't use buttons to get around this issue for my particular project either, this really does need resolving. 

Hi Luke! I do not have an update at this time as it is still in the hands of our QA Team. I will add a note so that the team is aware of more user impact.

Ah yes; another thread showcasing the excellent support for Articulate. Good job fixing the bug! Oh wait...