Anyone facing the same issue?
have you tried rollback or version control?
Careful with the rollback suggestion. Replit checkpoints roll back your code and files, not your Postgres data. Rolling back will not bring the rows back, and it can make things worse by reverting a schema your surviving data depends on. Worth knowing before you press it.
Two things to do in order, and the first one is time sensitive.
Stop writing to that database now. If it is the built in Replit Postgres, it runs on Neon, which keeps a point in time restore window. That window is measured from now, so every write and every app restart eats into how far back you can reach. Open the Database pane, look for restore or history, and pick a timestamp a few minutes before the data disappeared. Restore into a new branch rather than over the live one so you can compare before committing to it.
Second, check whether the data is actually gone or just unreachable, because those look identical from inside the app. An Agent run that regenerated your schema often leaves the old tables sitting there while the app queries new empty ones, so connect with SQL directly and list the tables rather than trusting the UI. The other common version is a swapped DATABASE_URL, where the app is pointed at a fresh empty database and your real one is still intact next to it.
If you have already restarted the app many times since the 14th, say so, because that changes which of these is still possible.