I’m experiencing an issue where the production database is not being created when I publish my application, despite clicking the “setup database” button when prompted by the agent.
Expected Behavior:
-
When publishing an app with PostgreSQL integration, both development and production databases should be created automatically
-
This used to work correctly in the past - both databases were provisioned without manual intervention
Current Behavior:
-
Development database: Created successfully ✓
-
Production database: Not created ✗
-
No production database tab appears in the Database pane after publishing
Steps to Reproduce:
-
Create a Replit project with PostgreSQL database integration
-
Work with agent to set up database using Drizzle ORM
-
Click the agent prompt to “setup database”
-
Publish the application
-
Check Database pane for production database
What I’ve Tried:
-
Republishing the application multiple times
-
Asking the agent to create production database (agent reports it doesn’t have permissions)
-
Checking Database pane for manual creation options
Technical Details:
-
Using PostgreSQL (Neon-backed) with Drizzle ORM
-
Development database works correctly
-
App is properly configured to use DATABASE_URL environment variable
-
Agent confirms code is production-ready
Impact:
Cannot use the production database with my published deployment. The app code is ready and will automatically use the production DATABASE_URL when available, but the database itself hasn’t been provisioned.
Question:
Has there been a recent change to how production databases are created? I understand from documentation that production database creation is currently in beta - is manual provisioning now required?