# Cannot create a production database when publishing (following a request by replit)

**URL:** https://replit.discourse.group/t/cannot-create-a-production-database-when-publishing-following-a-request-by-replit/11826
**Category:** Deployments
**Created:** [May 5, 2026, 8:58am UTC](https://replit.discourse.group/t/cannot-create-a-production-database-when-publishing-following-a-request-by-replit/11826 "2026-05-05T08:58:41Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![arthurjager](https://avatars.discourse-cdn.com/v4/letter/a/f19dbf/32.png) [@arthurjager](https://replit.discourse.group/u/arthurjager)
#### Post date: [May 5, 2026, 8:58am UTC](https://replit.discourse.group/t/cannot-create-a-production-database-when-publishing-following-a-request-by-replit/11826/1 "2026-05-05T08:58:41Z")

</div>

I have gotten a request to create a production website, as my app apparently still runs on a dev database. I have followed all the [instructions](https://docs.replit.com/cloud-services/storage-and-databases/create-production-database-when-publishing?utm_source=iterable&utm_medium=email) provided, but I cannot fulfill the requests, see attached.

There are no outstanding invoices..

Please advise..

Thanks.

 ![Scherm­afbeelding 2026-05-05 om 10.56.25](https://canada1.discourse-cdn.com/flex010/uploads/replit/original/2X/2/227c500473c8bab13b486dfcdbddaa6d43d9f4d5.png)

---

<div class="post-metadata">

### Author: ![yoyolyon](https://avatars.discourse-cdn.com/v4/letter/y/43a26b/32.png) [@yoyolyon](https://replit.discourse.group/u/yoyolyon)
#### Post date: [May 13, 2026, 10:19am UTC](https://replit.discourse.group/t/cannot-create-a-production-database-when-publishing-following-a-request-by-replit/11826/2 "2026-05-13T10:19:41Z")

</div>

Hi arthurjager,

It seems Replit currently has difficulties in deployment processes. I have a project I prepare for 6 months and tried to deploy 6 days ago. =\>I had the same kind of issue : I use the dev DB, but the publishing process does not create the prod DB.

Up to now, the support could not bring a solution to this, which is quite a problem since this problem may jeopardize months of work. The issue was supposed to be raised to L3-support, but no single news since sunday in spite of follow-up messages… ☹