"Remove from Game" not working, character shows back up upon refresh.

So I have a character sheet on my campaign that a player added, but it was an unneeded duplicate. I used the remove from game feature to remove it, and it goes away when I do that. Then if I refresh the page, the duplicate sheet reappears. I have gone through attempting to remove sheet half a dozen times. Please help!

Hi Shawn J.,  When this happens your only solution is to rename it and archive it. 

I've submitted this problem multiple times to Roll20 support (starting back in March 2025), both times I've been told this is an issue that can't be fixed. Because of this bug, I continue to amass more and more character sheets in my Roll20 game room. I now 85 character sheets in my game I am completely unable to get remove or delete.  The GM/creator of a Roll20 game should not be unable to control what character sheets or content is in their game.  This bug could be abused by ANY player who has joined the game (a past player or a even a new one on a public game), to spam hundreds of character sheets into a GM's Roll20 game against their will and the GM would be unable to remove the character sheets. Members of my D&D community who also use Roll20 have come up with what appears to be the issue: > When using the 2014 sheet and the old Character Vault, Roll20 retains some sort of link between the vault sheet and the one in the destination Roll20 game room. Even though the old school sheets/vault don't behave the same way new ones do (like updating edits across rooms and storage; being able to "remove from game"), that hidden link between the sheets means that the DM does not have permission to delete their room's version of the sheet while the character's version of the sheet still exists in the old Character Vault. As soon as the vault version is deleted, the sheet in the DM's room is now a free agent, no longer tethered to a players' special data, and is immediately deletable.

I'm in the same D&D community as JmanX, and our standard operating procedure is that DMs run multiple different one-shots out of their one base Roll20 room (so we have a lot of experience getting a wide array of players in and out of lobbies). "Rename and archive" is solution #3, in order of effectiveness. Here's my procedure for when player sheets "stick." Ask the player to self-initiate "Remove from Game" from their end. This is usually the most-frequently-effective option, as more players have migrated to using the newer sheets and newer My Characters page. This works even if the player created their character sheet from within your Roll20 room. If the player's desired outcome is deletion of the sheet, they will have to do this for themself once they have retrieved their sheet from your game. If the above doesn't work (because the player is using the old-school Vault import page), the solution JmanX described above works. Ask the player to clear out the detritus in their Vault, and then you will be able to clear out your Journal. Worst-case scenario is the full archive. I have only ever had one sheet glitch so fully that archiving is the only answer, and it was my own sheet that I tinkered with too hard, and during the introduction phase of the newer character sheet. I believe that this is an anomaly [due to the circumstances and timing of the bug], and unlikely to be replicated in current times The only "current era" player sheets I have had to archive are from players who are no longer reachable via Discord. Every time I have been able to contact a player with a "stuck" sheet, we have been able to get it removed.

I have a player who is experiencing this same issue.  We had him try everying reb_far suggested with no luck.  As the GM, I can't remove it.  The player can't remove it.  Seems like it is just stuck and dead in the water.  I opened a ticket a week ago and was told it was something only the devs could fix. In spending a couple of hours troubleshooting, the player in question was also able to delete a separate character sheet that I created in game and then shared with him through Roll20 Characters.  Seems like Roll20 should be recommending NOT using Roll20 Characters (or, at least, not importing those characters into games) until these issues are fixed.  That's what I'll be recommending to all of my players. -Adam ETA: One of the main issues that was causing frustration here was I use the whispertarget trick to allow players to whisper menus to themselves without bombarding the chat for everyone else.  No matter what we tried, this one player that was experiencing issues with the stuck sheet couldn't get the menus to be whispered to him.  Something to do with that stuck sheet threw everything into disarray for him.  The only thing that finally worked for this specific issue was kicking that player from the game (which broke the connection between the stuck sheet and them, but still did not allow me to remove it from the game) and then re-inviting them.  Since the player was no longer connected to the stuck sheet, the whispertarget macro worked once again. After spending two hours troubleshooting flawed Roll20 technology once again, I continue wondering why these features are not fully vetted at a large scale before they are pushed into production.