Deployement stuck

Question

Hello Railway team,

Four services in my production environment have been stuck in `INITIALIZING` for more than one hour. None of the deployments has entered the build queue, and Railway reports that they have no associated builds.

## Project details

* Workspace: `ainea26's Projects`
* Project: `FootyPass Production`
* Project ID: `e3d14050-e6bc-4e97-b1d9-bf6cdfee4dee`
* Environment: `production`
* Environment ID: `965409c2-608b-40bd-8a11-e6f18ec7f56f`
* Region: `EU West`
* Repository: `ainea26/FootyPass2-Backend`
* Branch: `main`
* Latest pushed commit: `ac2f638` — `fix: preserve imported TicketNetwork inventory`
* Public API: `https://apis.footypass.co.uk`

## Stuck deployments

All four deployments were created at exactly `2026-09-08 05:35:52 +03:00`.

### footypass-web

* Service ID: `5b3c47d7-fa24-49aa-aa3d-762535d73abc`
* Stuck deployment: `4d229894-0e87-457c-84bf-8ef860be40cd`
* Status: `INITIALIZING`
* Previous successful deployment: `a0b879ee-ff71-436b-b9c0-fc7fd2fb9084`
* Previous deployment time: `2026-09-07 17:49:04 +03:00`

### footypass-worker

* Stuck deployment: `23926af4-607f-42c6-8270-ec01256f7465`
* Status: `INITIALIZING`
* Previous successful deployment: `1e4a8949-7eb4-46fd-b626-0e80908330ce`
* Previous deployment time: `2026-09-07 17:49:04 +03:00`

### footypass-background-worker

* Stuck deployment: `e6c15e47-88fb-4adc-9cbb-1bd8e8174047`
* Status: `INITIALIZING`
* Previous successful deployment: `d4e63583-0d8f-41c7-bcd1-9aeb011c6e3f`
* Previous deployment time: `2026-09-07 17:49:04 +03:00`

### footypass-beat

* Stuck deployment: `275a5a9c-41a8-4d06-99d1-def38ba08e04`
* Status: `INITIALIZING`
* Previous successful deployment: `34b44672-34db-486f-8c85-1663806e4c2f`
* Previous deployment time: `2026-09-07 17:49:04 +03:00`

## Diagnostics

I ran:

`railway status`

All four application services reported:

`Online · Initializing`

I then ran:

`railway logs --service footypass-web --latest --build --lines 200`

Railway returned:

`Deployment does not have an associated build`

I also ran:

`railway logs --service footypass-web --latest --lines 200`

No deployment logs were returned.

I attempted one service-specific redeploy:

`railway redeploy --service footypass-web --yes`

This did not create a new deployment ID. The same deployment remained in `INITIALIZING`.

The deployment history still shows:

* `4d229894-0e87-457c-84bf-8ef860be40cd | INITIALIZING`
* `a0b879ee-ff71-436b-b9c0-fc7fd2fb9084 | SUCCESS`

## Application verification

The code itself appears healthy:

* Full Django test suite: `273 tests passed`
* `python manage.py check`: passed
* `python manage.py makemigrations --check --dry-run`: `No changes detected`
* The commit was pushed successfully and is present on `origin/main`.

Redis and Postgres both show `Online`. Existing Celery task records in Redis show successful execution, including the AI homepage task.

There is a scheduled Redis security patch notice, but its maintenance window is Saturday 10:00 through Sunday 18:00 UTC. Redis is currently online, so this does not appear related.

## Production impact

The previous successful deployments remain online, so there is currently no production outage. However, commit `ac2f638` has not been deployed, and all new deployments are blocked before the build stage.

Could you please investigate why these four deployments have not been accepted into the build queue, clear or cancel the stuck deployment group if necessary, and confirm when it is safe to trigger a new deployment?

Thank you.