The log here cuts off right where the actual error would be — yarn run build exit code 1 alone doesn't tell us why, the real reason is the stderr output right above the "Build Failed" line. Could you expand/scroll up in the build logs and paste the actual webpack/Strapi error text? That'll make this a lot faster to pin down.

In the meantime, the two most common causes of Strapi builds failing at this exact step on Railway:

Missing required Strapi secrets at build time — Strapi's admin panel build step often needs APP_KEYS, API_TOKEN_SALT, ADMIN_JWT_SECRET, TRANSFER_TOKEN_SALT, and JWT_SECRET set as env vars even during build, not just at runtime. If the template didn't auto-generate these (or they got wiped), the build step can fail. Worth checking your service's Variables tab for all five.

Node version mismatch — your log shows Node 22.23.2 being installed. Strapi (especially v4) has fairly strict engines requirements and some versions don't officially support Node 22 yet — if your package.json doesn't pin a supported Node range, Railpack may be grabbing a newer Node than Strapi's build tooling actually supports. Worth checking what Strapi version the template uses and whether it lists Node 22 as supported; if not, pinning "engines": {"node": "18.x"} or "20.x" in package.json is the fix.

I don't think Node 22 is the problem here.. the template itself is explicitly asking Railpack for >= 22.x.x, and Railpack is correctly installing 22.23.2

The useful error is missing from this log! It jumps straight from:

yarn run build

to:

Build Failed: build daemon returned an error

Could you open that build step and paste the output from yarn run build itself?

exit code: 1 doesn't show what Strapi actually failed on. Since this is the Railway Strapi template failing out of the box, that output should be enough to tell whether it's the template or the deployment config..