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

• 🧵 Build stuck at Fetching Snapshot

• 🧵 Metal Build Environment enables randomly?

• 🧵 Services keep switching the Metal Env option to True

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

the "Activity" shows the changes should have been applied. Yet they're not.

Now they've all switched back. I have just checked the services I was able to change. They're all back to Metal Build Environment. They switched on their own.

Hello,
We're in the process of rolling out metal build environment as the primary builder for everybody. As a result, your services are going to have it enabled. Are you able to provide the log/error you see on metal builders? Would love to fix this.

Hi. Thank you for a fast response. But this is contrary to the docs. Why is there a toggle if I can't disable it? I've just wasted 30 min on this. Do not appreciate misleading UI. If there was a note, sure. I literally just pitched Railway to our manager for a large project. These things must be documented.

Sure.

1st service failure:

scheduling build on Metal builder "builder-gnqfra"

[snapshot] received sha256:eee10ec2c4eb7eb701da3f04f4a78342ef440359ec0a4c798601ce356abdb7af md5:957a460b05b44e9751ad3a3cf0000a32

receiving snapshot3.2 MB2.2s

analyzing snapshot3.2 MB39ms

uploading snapshot3.2 MB58ms

scheduling build on Metal builder "builder-gnqfra"

fetched snapshot sha256:eee10ec2c4eb7eb701da3f04f4a78342ef440359ec0a4c798601ce356abdb7af (3.3 MB bytes)

fetching snapshot3.2 MB335ms

unpacking archive4.2 MB52ms

using build driver railpack-v0.15.1

╭─────────────────╮

│ Railpack 0.15.1 │

╰─────────────────╯

↳ Detected Node

↳ Using npm package manager

↳ Found workspace with 4 packages

Packages

──────────

node │ 22.21.1 │ railpack default (22)

Steps

──────────

▸ install

$ npm ci

▸ build

$ npm run build -w @planstream/landing

Deploy

──────────

$ npm run start -w @planstream/landing

load build definition from ./railpack-plan.json

0ms

mkdir -p /app/node_modules/.cache cached

0ms

install mise packages: node cached

0ms

copy package-lock.json, package.json, packages/core/package.json, packages/service/package.json, packages/web/landing/package.json, packages/web/webapp/package.json, packages/service/prisma, packages/service/src/generated/prisma

3s

npm ci

20s

added 706 packages in 19s

copy / /app, .

1s

npm run build -w @planstream/landing

24s

npm warn config production Use --omit=dev instead.

> @planstream/landing@0.0.0 build

> next build --turbopack

▲ Next.js 15.5.6 (Turbopack)

Creating an optimized production build ...

✓ Finished writing to disk in 53ms

Turbopack build encountered 2 warnings:

[next]/internal/font/google/noto_sans_aa601580.module.css

Error while requesting resource

There was an issue requesting https://fonts.googleapis.com/css2?family=Noto+Sans:wght@100..900&display=swap

[next]/internal/font/google/outfit_2282136a.module.css

Error while requesting resource

There was an issue requesting https://fonts.googleapis.com/css2?family=Outfit:wght@100..900&display=swap

> Build error occurred

[Error: Turbopack build failed with 2 errors:

[next]/internal/font/google/noto_sans_aa601580.module.css

next/font: error:

Failed to fetch Noto Sans from Google Fonts.

[next]/internal/font/google/outfit_2282136a.module.css

next/font: error:

Failed to fetch Outfit from Google Fonts.

]

npm error Lifecycle script build failed with error:

npm error code 1

npm error path /app/packages/web/landing

npm error workspace @planstream/landing@0.0.0

npm error location /app/packages/web/landing

npm error command failed

npm error command sh -c next build --turbopack

Build Failed: build daemon returned an error < failed to solve: process "sh -c npm run build -w @planstream/landing" did not complete successfully: exit code: 1 >

2nd service failure:

scheduling build on Metal builder "builder-gnqfra"

fetched snapshot sha256:69681049cd7cbd4069d4e75ca77f99a3ccda898e772eeabb984895b4b1c84c10 (3.3 MB bytes)

fetching snapshot3.2 MB1.4s

using build driver railpack-v0.15.1

╭─────────────────╮

│ Railpack 0.15.1 │

╰─────────────────╯

↳ Detected Node

↳ Using npm package manager

↳ Found workspace with 4 packages

Packages

──────────

node │ 22.21.1 │ railpack default (22)

Steps

──────────

▸ install

$ npm ci

▸ build

$ npm run build --workspace=@planstream/landing

Deploy

──────────

$ npm run start --workspace=@planstream/landing

Build Failed: build daemon returned an error < failed to solve: frontend grpc server closed unexpectedly >

and there's more

Completely understand the frustration and would love to help get this sorted out. Could I possibly get a link to the service having issues?

I am more frustrated with the lack of notice/documentation about these sudden changes rather than any crashes. The crashes have now resolved themselves after I redeployed them. However, this shows there's still some instability. To confirm, are you saying I will not be able to disable this?

What kind of link is it that you need?

Thanks for the swift follows ups however. That's really nice!

Of course! I'll be honest I don't have the best answer and don't want to give something inaccurate on that front. I've asked internally how the rollout looks and will let you know as soon as I hear back.

For now I'm glad to hear its working and we want to keep fixing any and all of the bugs with the new system so keep bringing em up as you see them!

Thanks. Apologies for an abrupt messages earlier. I am still happy to provide those links if you want to investigate deeper why the builds failed.

I don't blame you and all is well! If you could send me the link to the deployment/service that had those errors that would be amazing!