Provision gets stuck indefinitely without any status updates or error information

Deployments
1

Is anyone else having issues with Provision?

Since last month, whenever I try to publish a new version, the process gets stuck on “Provision” indefinitely. I can cancel and retry multiple times, but it never goes through.

I contacted support, and they suggested shutting down (deleting) the app and deploying it again. This workaround does work, but it’s extremely inconvenient.

After deleting and redeploying, everything works fine , until I need to publish another update. Then the same issue happens again: it gets stuck on Provision forever. Basically, for every update, I’m forced to delete the app and recreate it.

This is not a viable solution for me because I have multiple payment webhooks configured. Every time I delete the app, I need to reconfigure everything.

Last week, after deleting the deployment and trying to deploy again, I even got an error saying the domain was already in use.

Is anyone else experiencing this?

It’s happening again right now.

Last week I deleted (shut down) the deployment and published a new version successfully. Today, when trying to update again, it’s stuck on Provision once more.

2

Having the same problem, stuck on Provision for 3 days. Tried to restart the process like 4 times, but every time with the same outcome.

3

Did we ever figure out what the issue? I’m having the same problem and the Shutdown option is not a fix. It didn’t help and it deleted all my api production connections. I’m never doing that again!

4

Hey, here is what worked for me:

If it is failing after trying to run a migration script –> run the script directly into your production database through the SQL Console

(just make sure to look at what it does to not break stuff in production)

1 Like
5

I’ve had the same problem and it seems to be hanging either, creating, altering or deleting database tables and columns.

As a work around I manually executed the database changes directly into the SQL console on the production database. I was then able to republish.

I’d imagine this is a bug that needs investigating. Support are very slow to respond.