Start 2025 on time and up to date! Seamlessly integrate your calendars into Dropbox with these simple steps! 📆
Forum Discussion
Solved
Dropbox Replay stuck on unexpected error after re-inviting user to Business team
Recently re-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 us...
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.
After doing so it looked like it generated a new auth code so I now have access to Replay.
Nancy
Dropbox Staff
Dropbox StaffHi vxville, and welcome aboard the Community!
Just to clarify, was it your own Dropbox account that was accidentally removed from the Business team or another user’s? Also, are you an admin on the team or a team member?
Has the Dropbox account that was previously removed been successfully re-added to the team or is it in pending state still?
Finally, does the same error persist on different browsers? If yes, I’d like a full screenshot of it to have a visual.
Let me know when you’ve got more info.
Hi,
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.
Dropbox account has been re-added to the team once making another account under the same email.
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
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.
After doing so it looked like it generated a new auth code so I now have access to Replay.
