We’re seeing Railway environment staged-change workflows get stuck indefinitely in APPLYING for production. Project ID: 0c92aacc-553a-4b77-b944-f276f9b7eafd Environment ID: 605e5949-b246-4396-8995-5d746de0e913 Symptoms: - Dashboard shows “Applying N changes” for services, including services that have since been deleted. - Deleted services still appear to have pending apply workflows tied to them. - While these workflows are stuck, we cannot reliably apply variables or shared variables from the dashboard/API. - Public GraphQL variable/staged patch APIs appear to enqueue commitChanges workflows that remain stuck. - We found internal dashboard links referencing Temporal workflows like: commitChanges/605e5949-b246-4396-8995-5d746de0e913... - Manual service creation/deploy via dashboard-style service create + serviceInstanceUpdate + serviceInstanceDeployV2 can work, but staged environment patch commits appear wedged. Can you clear/cancel the stuck commitChanges workflows for this environment, and confirm whether environmentPatchCommitStaged / variableCollectionUpsert can leave an environment permanently stuck in APPLYING when target services are deleted? We also need guidance on the correct API sequence for creating a Docker image service with start command + variables without leaving pending staged changes.

Staged-change workflows get stuck indefinitely in APPLYING

horizonxp

PROOP

3 months ago

We’re seeing Railway environment staged-change workflows get stuck indefinitely in APPLYING for production.

Project ID: 0c92aacc-553a-4b77-b944-f276f9b7eafd

Environment ID: 605e5949-b246-4396-8995-5d746de0e913

Symptoms:

Dashboard shows “Applying N changes” for services, including services that have since been deleted.
Deleted services still appear to have pending apply workflows tied to them.
While these workflows are stuck, we cannot reliably apply variables or shared variables from the dashboard/API.
Public GraphQL variable/staged patch APIs appear to enqueue commitChanges workflows that remain stuck.
We found internal dashboard links referencing Temporal workflows like: commitChanges/605e5949-b246-4396-8995-5d746de0e913...
Manual service creation/deploy via dashboard-style service create + serviceInstanceUpdate + serviceInstanceDeployV2 can work, but staged environment patch commits appear wedged.

Can you clear/cancel the stuck commitChanges workflows for this environment, and confirm whether environmentPatchCommitStaged / variableCollectionUpsert can leave an environment permanently stuck in APPLYING when target services are deleted? We also need guidance on the correct API sequence for creating a Docker image service with start command + variables without leaving pending staged changes.

Closed

5 Replies

petersim1

PRO

2 months ago

Also experiencing issues where applying changes gets hung up. Not sure if it's with deploying a new service, or for updating variables.

noahd

EMPLOYEE

2 months ago

Hey! Aware of this and actively working on a fix.

lumberman

PRO

2 months ago

same problem for us. Blocked on this. Can't do anything until resolved. if you have a quick reset/fix please let us kno

noahd

EMPLOYEE

2 months ago

Hey there!

We've rolled out some changes that should resolve this. Can you let me know if you're still running into it?

lumberman

PRO

2 months ago

yes it still stuck at 'applying 1 change' after I edit project variables via RAW EDIT option.

Welcome!