Tokens lose their saved values after a day

Hi everyone, I have noticed that in my game, whenever I prepare a bunch of tokens, a lot of them (about half) lose all their saved values and go back to being empty tokens. I saw that happening before for some time but usually with just a single token, which can be redone quickly, but at this point I'm doing half the work twice and it really bugs me. From what I can tell, all the tokens save correctly and when I restart my browser and open the game again, everything is still saved correctly, but the next day what I saved is mostly gone. The values that I'm adding are usually token name as well as text or number values in bar one and two. If the token had a different name before, it even goes back to its old name. Does anybody have an idea what might be causing this or what I could try to do about it? I really hope to find a solution, because at this point I'm better off waiting rather then doing everything twice.

Do you mean the same instance of the token is changing properties? Or when you drag a new copy out to the map? If the latter, chances are the default token has not been updated with the latest values. 

It's the same instance of the token. If I don't change the default token it goes back to default and if I change the default token it goes back to empty and the default is saved as empty. Odd thing is that not all tokens go back. I use a multi-sided token with the name "location" saved as deafult for my map markers. Yesterday I dragged like 30 or so on my new map and changed 9 of them to have thier respective names, as well as a short description saved in bar 1 and links to handouts saved in bar 2. Via token action "&{template:default} {{name=@{selected|token_name}}} {{@{selected|bar1}}} {{@{selected|bar2}}}" the players or myself can then display the information in chat to read which I test in order to see if the handout links work correctly. Out of these 9 today 4 of them are back to default with the name "location" and both bars empty only displaying the correct side of the multisided token. That's just one instance but it's the most noticeable so far.

Something of note might be that if I change a token that had this issue once, it will always go back to default the next day and I have to delete it and drag it on the map again before adding the same information again.

Ok so that does sound unusual (and frustrating!) and probably warrants a Help Desk ticket unless someone else chimes in with a solution.

Hi PRJr0815! This sounds like interaction with some automation gone awry. If using an extension that alters the behavior of Roll20, try turning that off. Also, are you using any APIs that affect token values, like SpawnToken or Health Auras?

I'm not using any browser extensions but I have a couple of API scripts installed in that game. I use TokenMod, StatusInfo, GroupCheck, GroupInitiative, ApplyDamage, SpawnDefaultToken, libTokenMarkers and TokenNameNumber. I don't use any commands to set up the tokens in question tho or at all with these tokens, since they are just map markers. No idea if the scripts would mess up the tokens on their own.

I can only speak to SpawnDefaultToken: If you are not using any !Spawn commands in this testing, it will not affect any tokens or sheets.

I should have clarified that. HealthAuras is a passive, continuous adjuster. SpawnDefaultToken would require a command if it were the culprit. And no intent to denigrate either script, just mentioning a few that can modify tokens without a specific modification command being issued, a la token-mod. This sort of sporadic and inconsistent behavior is very hard to pin down, because you can't run verification test on it. I don't see anything in your list that stands out, though. I haven't run into the issue myself, and I have map pins that are years and years old.