**Plain reading:** You're running a SQL query that references a column "user_id" on the "orders" table, but that column isn't in the table. **Most likely cause:** A database migration that adds the user_id column hasn't been applied in this environment. The code was deployed with the assumption that the column exists. **First thing to check:** Compare the schema of orders in this environment against your migrations directory. Run \d orders in psql against the production database; check whether user_id is listed. **Second thing to check (if the first was inconclusive):** Look at the migration log table (whatever your migration tool uses — alembic_version for Alembic, schema_migrations for Rails-style tools). The expected migration should be present. If it's not, the deploy didn't run migrations. **Less likely possibilities:** 1. The column was added but with a different name (userId, user, customer_id). Check the migration file for the actual column name. Distinguishes from cause #1 by the migration table showing the migration ran but the column being named something else. 2. You're connected to the wrong database. Distinguishes by SELECT current_database() returning something unexpected. **Common false leads:** - ORM cache: asyncpg doesn't cache schema in a way that would cause this. Ignore. - Permission issues: a permission issue would produce a different error class. Ignore.