a0f3572b-295e-4a43-b776-ce352a4d0980

that's interesting 🤔

Does it continue to say "Waiting for build to start" if you abort and redeploy?

For example

oh I see

Not sure if aborting and redploying works, I can test that later on

Sounds good

how often do you encounter this issue?

I think for this project almost all builds at the moment

If I look into older builds I see the same although sometimes it is a smaller delay

I'll go ask around and see if I can figure out what could be the cause
if all else fails then I'll flag this issue to the team for you

Thanks

Still having issues on the project that it says Waiting for build to start… for 3 mins

I have a new record on a different project, already 17 min waiting to start <:mildpanic:804271964587819059>

Hey pepijn, sorry for the late reply
I did ask around but couldn't find any possible reason why this could be happening

Mind providing some deployment ids of deployments that get these delays?
I'll then flag the team for you

You can get the deployment id of a deployment by viewing the deployment's logs / details and then clicking on the id at the top ( see screenshot below )

• 5ab04331-160c-443d-857b-df1e94146f84 (about 3 min delay on build start)

• 1fcb0061-98bf-422f-bb71-e1923ec47d1b (about 4 min delay on build start)

I will look out if I see any other pop-up

Any update by the team?

Sometimes it also shows this

are you sure you don't have any CI running?

Hey there, apologies for the delay, we're looking into it currently, will report back

Indeed the waiting in the screenshot is of when CI is running, but still after that the waiting on build to start delay of 3 mins persists

perhaps github is slow to let railway know that ci has finished, or maybe railway does polling with 3 minute intervals?

The delay was already happening before there was any CI in place

gotcha

Can you disable the CI and push again?

If there's already a wait for CI, it may deprioritize the build start

Sure, but same thing as earlier. Deployment ID: aa65e129-44f1-4dfc-9f22-2c2824bb6c11

It seems a pretty consistent 3 min wait time

Also the UI in railway keeps telling met to not set a build command, although none is set

Any updates? Issue still remains

Hey, I've responded to you over Slack on this. Let's keep the discussion there as there's another issue you're having

To circle back for anyone else running into this thread. The issue was the repository was pretty big in size, we cleaned/reduced it where possible and now the builds start quickly again!