Hey there! We've found the following might help you get unblocked faster:

• 📚 Add a Pre-Deploy Command

• 🧵 Predeploy command logs missing

• 🧵 Pre-deploy command failed without logs

If you find the answer from one of these, please let us know by solving the thread!

It sounds like an issue with your migration script sending SIGINT to the container when it exits on a redeploy. I'd expect migrations not to run on a redeploy, but rollbacks of stateful workloads can be a little tricky.

```
@headlinersapp/common db:migrate: Exited with code 0

Stopping Container
```

I don't think there's enough logging here to understand what is happening during your db:migrate step, but something is clearly breaking. Have you added more tracing to see what's going on with your migrations?

I think I'm still running into this issue...

I've been keeping an eye on this with additional logs and guards. From what I gather, my guess is that the database connection wasn't closing so the process wouldn't quit. I've since added an explicit exit which isn't ideal but I haven't have the pre-deploy hook hang at all in regular deploys.

That said, I tried a rollback again today and same issue... hanging on the "completed" script. There were no added migrations or changes to the step between the current and target deployment. I can't tell 100% but I believe this was the first stalled deploy: 10715c3a-bea9-4098-ba21-db694d615690

I've tried deploying latest and additional commits but now the workflow seems stuck on "Waiting for previous deployment". There aren't any pending deploys.

Any assistance with getting the latest commit deployed would be appreciated -- production is down so I'd like that resolved ASAP, the rollback issue is somewhat of an aside. Thanks!

Hi there!
We identified and fixed something earlier today which might have been the cause of this. Are you still running into these issues?