my deployments are failing without any error logs
Anonymous
PROOP

3 months ago

id- c63241d2-b5d0-447c-af1a-9b11034a3685,

id- 7b78b02c-f387-4cc0-8336-b598e5bb3c13

Solved$20 Bounty

Pinned Solution

Anonymous
PROOP

3 months ago

Why overrides.ioredis in backend/package.json

bullmq depends on ioredis but ships a different version nested under

bullmq/node_modules/ioredis. TypeScript treats nested vs root ioredis

type defs as distinct types — passing a root Redis instance into a

bullmq Queue fails type-check even though runtime works. The override

forces all transitive ioredis references to dedupe to our root pin.

5 Replies

Railway
BOT

3 months ago

This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.

Status changed to Open Railway 3 months ago


Anonymous
PROOP

3 months ago

my application running just fine in local


Anonymous
PROOP

3 months ago

Why overrides.ioredis in backend/package.json

bullmq depends on ioredis but ships a different version nested under

bullmq/node_modules/ioredis. TypeScript treats nested vs root ioredis

type defs as distinct types — passing a root Redis instance into a

bullmq Queue fails type-check even though runtime works. The override

forces all transitive ioredis references to dedupe to our root pin.


Status changed to Open sam-a 3 months ago


Anonymous
FREE

3 months ago

Build succeeds but deployment fails before container startup. Runtime logs are empty and application works locally. Could you check whether image manifest/imageDigest resolution is failing for deployment ID XXXXX?

git commit --allow-empty -m "trigger redeploy"

git push


Anonymous
FREE

3 months ago

git commit --allow-empty -m "trigger redeploy"

git push


dev-charles254
PRO

3 months ago

Hey! Since your build succeeds but it fails instantly before container startup with zero logs, try these quick fix

Check Root Directory settings: Since you mentioned a backend/ folder, go to your Railway Service Settings and double-check that your Root Directory and Watch Paths are explicitly pointed there. Auto-detection sometimes misses this, causing silent crashes.


Status changed to Solved passos 2 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...