# Replit — Data Loss: a sad tale with a happy ending

- Company: Replit (replit.com)
- Announced: 2021-09-10T22:00:00+00:00
- Category: not stated
- Coverage: not counted
- Announcement: no
- Group: routine
- Source: https://replit.com/blog/data-loss
- Record: https://forck.live/items/18145-data-loss-a-sad-tale-with-a-happy-ending
- Subject: Replit Agent

Replit discovered and fixed a data loss bug affecting some users, where repls could be empty or missing changes after reloading. The root cause was a bad interaction between Golang's exec.Cmd, a filesystem snapshot tool, and system resource pressure. Mitigations were in place by the end of July, and subsequent improvements made repls load faster and more responsive.

## Evidence

Verbatim from https://replit.com/blog/data-loss:

> Earlier this year, we discovered that we were losing data for some of our users. This manifested as either repls being completely empty after reloading, or some of the changes to files not being present after reloading.

---

Record: https://forck.live/items/18145-data-loss-a-sad-tale-with-a-happy-ending
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md