[▲ Vercel Community](/) · [Categories](/categories) · [Latest](/latest) · [Top](/top) · [Live](/live) [v0](/c/v0/59) # Restoring a previous version in v0 results in incorrect version history numbering 55 views · 0 likes · 6 posts A.derk (@agustinkcht) · 2026-01-28 this actually has been happening for weeks. basically, restoring a previous version of a project completely messes up the version history, altering the numbers and adding tens of new “versions”. For example (this happened 5 mins ago) i was on the v7 of a project. I went back to v6 (which should have generated a v8), and i got a **v50** created with tens of extra versions that didn’t exist. anyone with the same problem? Pauline P. Narvas (@pawlean) · 2026-01-28 I've not seen this issue - can you share a link with us? A.derk (@agustinkcht) · 2026-01-28 Of course. What happens is, new versions that shouldn’t exist (tens of them) are added to or removed from the version history. I noticed this bug doesn’t happen until i restore a project to a previous version. From then on, it starts happening, and happens multiple times. Sometimes it adds versions, sometimes it removes versions. But i always end up with a huge version history, and confusion about which version is which. Look, this is the project i wrote about some hours ago. - The bug started when i was in V7 and restored V6. It generated a V50. - It went up and down with use. - Look how at 16:50 it was v121 - 20 mins later (1 or 2 generations later, it’s v141) Probably, i’m around v20 of this project, and it currently says v141. If you need more info, just tell me and i will attach what’s necesary!   Pauline P. Narvas (@pawlean) · 2026-01-29 Thank you for sharing a screenshot and examples! Helps a ton. We shipped this change yesterday, I wonder if they are related? How is it today? https://x.com/v0/status/2016573614133563544 A.derk (@agustinkcht) · 2026-01-30 Hi! Still having the issue. Look, i restored a version and there you have it clearly: it should be v216, but it generated a v242. It’s so strage. I’m probably around v40/50 of this project, but i ended up in v242. It certainly looks like im grinding it😂  Pauline P. Narvas (@pawlean) · 2026-02-04 Thank you for flagging! Shared with the v0 team.
