Advanced Replay

[Dannie Heinzen]

Recentlyre-invited an email to an Advanced account after removing mistakenly, not able to access Replay and get stuck on "Unexpected error". All the previous shared links do still work outside of using the account email but not able to access Replay whatsoever. Other email members attached to the account can access as normally and can access the links. Just the relinked account that is affected. Wouldn't be surprised if I'm not able to access the previous uploads on Replay but being able to use going forward would be the main issue to resolve.

Turns out I was able to resolve this by clearing/deleting the site cookies and cache on the Dropbox Replay page using site settings (on 'replay.dropbox.com' and not 'dropbox.com') and now seems to work fine.

Did this post help you? If so, give it a Like below to let us know.

Need help with something else? Ask me a question!

Find Tips & Tricks Discover more ways to use Dropbox here!

Interested in Community Groups? Click here to join!

It was another user that was mistakenly removed from the team, which of course got rid of their access and login. I am an admin on the team and now have made that same user an admin also, although they were just a team member prior.

The same error doesn't seem to be there when using other browsers so it takes me straight to it although it's empty, so nothing from before other than the welcome to Replay video. Should also clarify, all the shared links from the account before removal on Replay do still seem to work

I wanted to let you all know about the new Dropbox Replay group we recently launched here on the Dropbox Community. The group will be a great place to chat with other Replay users, discover tips and tricks, and even connect with some members of the Replay team. You can join now by following this link and hitting the "Join group hub" button!

I work at Replay.io, and I've spent all of this year building some incredibly advanced React debugging features that make use of our time-traveling backend API. The biggest one is our React DevTools integration. Early in 2023, I wrote a post for the Replay.io blog on How We Rebuilt React DevTools with Replay Routines, which recapped the initial working version. I've spent much of this year improving on that and building other related features.

At React Advanced, I got to share details on how the React DevTools work internally, and dive into how we extract React DevTools component tree data from recorded React apps using a combination of custom Chrome modifications and backend post-processing "routines" that leverage our time-travel API. Along the way, I showed off some crazy tricks like serializing JS functions as strings, sourcemapping original component names from production apps, and generating sourcemaps for React itself!

It appears the zap is resending "failed" webhooks 10minutes after the initial send, which it should not be doing since "Never Replay" is enabled, which is causing the 3rd party automation which logs to the Google sheet to run twice since it gets triggered from the webhook sending from Zapier

What I have found out after checking our logs is actually related to the way our delay process is designed. In the back end of things, Delay does a very similar process than a replay would.

After the delay step hits the release time, the process goes over any 'unplayed' steps in the Zap until it hits the delay stage and then continues with the rest of the workflow.

Because our process does not recognize the timeout as an actual error, it defaults to try sending your POST again as it was never technically labeled as an 'error' as such. Since the HTTP call has no status, it tries to process again.

It's possible that creating a sub-zap with a delay and subsequent steps might help in this situation. The idea behind this is to isolate the delay and subsequent steps from the main zap. This way, if there is a timeout on the webhook, the sub-zap will not be triggered again.

This method essentially makes your main zap and sub-zap work together, but the sub-zap will only run when it's triggered by the main zap. If the webhook times out, it shouldn't trigger the sub-zap again.

Prelude: My project needs a Pause/Play button and a Rewind button. I am creating a project in Captivate 2017 where each slide needs to play to the end of the slide before the on screen buttons are enabled on the user's first visit. On the second visit, everything needs to be enabled at the beginning of the slide. I tried using Conditional statements where on the first pass, everything is Disabled in the On Enter Advanced Action, then after a Delay Next Action By action everything is enabled. Because my project has a Pause/Play, the inability to control the Delay Next Action By action with a Pause command means that I am now trying to use JavaScript timers with my On Enter Advanced Action that will enable the interactions when the timers run out.

But this only brings me to the first frame of the slide and does not trigger the slide's On Enter Advanced Action again, meaning that the Javscript for the timers are not triggered again, which would reset the timers for me.

Question: I have looked into JavaScript where you can use the line cp.runJavascript(cp.model.data.objectname.oca); to trigger an Advanced Action on a slide's object, but is there a way to run the JavaScript for the slide's On Enter Advanced Action using a similar line of code? I am hoping to add something with that functionality as an Execute Javascript action to the above Replay button Advanced Action, so it will jump to the initial frame of the slide, and also trigger the On Enter Advanced Actions, so that on a first visit, everything will still function how I need it to. If that makes sense.

I also found the below code that would allow me to find the slide's ID, which I was hoping I could put into the cp.runJavascript(); code and it would trigger the On Enter Advanced Action, but I have not been able to make that work either.

You also need some logic to help with when users resume the lesson, by that I mean leave and the resume at a bookmarked location. I do the same thing, bounce off slide 1 to make sure all the javascript and advanced actions are set up before the user starts view the lesson.

I have seen your tutorials on micro nav, very helpful. I think the issue the original poster and I both had was that we had actions on Enter Slide, which is not triggered when you send the playhead back to the first frame of the slide.

Sorry, I did explain what has to happen in that case, that is why I rewind the playhead to a couple of frames before the first frame of the slide, to allow the On Enter action to be done. I described both scenarios extensively in the Replay button post.

The blank slide at the beginning of the course has an On Enter action that sends the user back to the last visited slide. Since the user is entering the slide and its visited variable is now set to 0, it plays as if entered for the first time. This blank "bounce" slide can serve as the replay mechanism for all the slides in the course.

If you want to trigger an action with JavaScript, put a tiny transparent clickbox in a corner of the slide where users won't accidentally click. The clickbox action can be a duplicate of the On Enter action, or whatever subset you need. Use the following to trigger the clickbox:

Lilybiri, I did see the links you provided before bringing this question to the discussion board. For your solution to the micro navigation, I did go that route initially to double up the next button and have one hidden until the second visit, but the client wants everything disabled on the slide until the audio finishes the first time around, but then everything enabled from the start of the slide the second time around. So that means I could have a slide with numerous buttons that would all require a second version. I was trying to avoid all of the extra work by using timers. I'm tasked with building hundreds of slides with potentially multiple interactions on each slide that need to follow these rules, so I am looking for the most efficient means to get everything to work.

I also fought with a situation where I had narration and buttons that should appear/be enabled in a sequence the first time around, but no narration and full button functionality the second time through a slide. I found the Delay action didn't work for me since the advanced action containing the Delay statement would continue to run even if the user clicked another button. The first action was not aborted when the second action started and they overlapped each other. Without seeing your exact situation, the best solution seems to be to have elements disabled/enabled or hidden/shown through conditional actions that have the slide counter as the condition.

This gets a slides current index. We subtract 1 because we want an array based index starting from 0 whereas this method returns the actual slide number in Captivate aka the cpInfoCurrentSlide variable value.

This training is about 1 hour and 25 minutes long. The small group (breakout room) exercise time has been edited from the replay. Attend a live webinar so you can ask questions and participate in the small group exercises with people from all over the world.

Gather up your facilitators and watch the training together and do the small group exercises as a team. Or send the link/password to your facilitators to watch on their own and set up a time to discuss the information at a later date. Whatever works best for your organization.

3a8082e126