Hi Neon team 👋
Hi Neon team 
Project: autonoma_db
Database: Neon PostgreSQL (connected via Prisma and hosted app on Railway)
Context:
We’re using Neon as the main database for our app Autônoma.app, which is hosted on Railway.
Even after migrating everything to Neon, the app still shows “phantom” professional profiles that are not in our Neon database.
We need help with:
1. Confirming if the database autonoma_db is fully connected and synchronized with Prisma.
2. Checking if there is any cache, old replica, or outdated version still active on Neon or Railway.
3. Guidance on how to safely clear all test data (truncate tables + restart IDs).
Tech environment:
Node.js + Express + Prisma
PostgreSQL (Neon)
DATABASE_URL set with SSL required
Our goal is to make sure the app reads only data from Neon and not from any old or cached source.
Thanks in advance for your support
— Kadu Costa (Autônoma.app)
Project: autonoma_db
Database: Neon PostgreSQL (connected via Prisma and hosted app on Railway)
Context:
We’re using Neon as the main database for our app Autônoma.app, which is hosted on Railway.
Even after migrating everything to Neon, the app still shows “phantom” professional profiles that are not in our Neon database.
We need help with:
1. Confirming if the database autonoma_db is fully connected and synchronized with Prisma.
2. Checking if there is any cache, old replica, or outdated version still active on Neon or Railway.
3. Guidance on how to safely clear all test data (truncate tables + restart IDs).
Tech environment:
Node.js + Express + Prisma
PostgreSQL (Neon)
DATABASE_URL set with SSL required
Our goal is to make sure the app reads only data from Neon and not from any old or cached source.
Thanks in advance for your support
— Kadu Costa (Autônoma.app)
