Worker service failing to initialise
gholimoli
HOBBYOP

a year ago

after my latest commit the worker service is failing to initialise with this message: "Cannot create code snapshot right now, please review your last commit or try again

If this error persists, please reach out to the Railway team." However the web service from same commit is being built and deployed with no issues. i have not changed any config files or settings.

Solved

18 Replies

Railway
BOT

a year ago

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

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


Railway
BOT

a year ago

Hello!

We're acknowledging your issue and attaching a ticket to this thread.

We don't have an ETA for it, but, our engineering team will take a look and you will be updated as we update the ticket.

Please reply to this thread if you have any questions!


Hey there, I see your workload live but escalating anyways so we can get to the root of the issue and fix it.


Status changed to Awaiting User Response Railway about 1 year ago


prepora-ai
HOBBY

a year ago

I am also getting same issue.


Status changed to Awaiting Railway Response Railway about 1 year ago


prepora-ai

I am also getting same issue.

Can you provide your project Id?


Status changed to Awaiting User Response Railway about 1 year ago


diamoundz
FREE

a year ago

I'm getting the same issue


Status changed to Awaiting Railway Response Railway about 1 year ago


diamoundz

I'm getting the same issue

Project ID please


Status changed to Awaiting User Response Railway about 1 year ago


cattamer
PRO

a year ago

I have the same issue: 2abe3f59-872c-4759-bdc6-a22770bbad46


Status changed to Awaiting Railway Response Railway about 1 year ago


cattamer

I have the same issue: 2abe3f59-872c-4759-bdc6-a22770bbad46

https://railway.com/project/2abe3f59-872c-4759-bdc6-a22770bbad46/service/7113a7d0-9ada-48ad-b7a2-b0c0408e36eb?environmentId=aaaa4d42-64ed-45fe-942a-fc169b76a5da

Can you kick a deploy in this duplicated service I made for you? I want to see if this narrows down the bug.


Status changed to Awaiting User Response Railway about 1 year ago


angelo-railway

<https://railway.com/project/2abe3f59-872c-4759-bdc6-a22770bbad46/service/7113a7d0-9ada-48ad-b7a2-b0c0408e36eb?environmentId=aaaa4d42-64ed-45fe-942a-fc169b76a5da> Can you kick a deploy in this duplicated service I made for you? I want to see if this narrows down the bug.

cattamer
PRO

a year ago

Done! unfortunately no improvement.


Status changed to Awaiting Railway Response Railway about 1 year ago


cattamer

Done! unfortunately no improvement.

cattamer
PRO

a year ago

Any ETA?


robfromnewground
PRO

a year ago

I'm getting the same error message


cattamer

Any ETA?

Your railway.toml file appears to contain invalid configuration:

 deploy.restartPolicyType: Invalid input

Can you please ensure the type is correct and conforms to https://backboard.railway.app/railway.schema.json?


Status changed to Awaiting User Response Railway 12 months ago


robfromnewground

I'm getting the same error message

Could you open a new thread please?


For those having the same issue:

  1. Try removing "config as code" from your service settings and see if the deployment goes through
  2. If it does, ensure the config as code file you're providing conforms to our schema

Thanks!


ray-chen

Your railway.toml file appears to contain invalid configuration: ``` deploy.restartPolicyType: Invalid input ``` Can you please ensure the type is correct and conforms to <https://backboard.railway.app/railway.schema.json>?

cattamer
PRO

a year ago

Yes! This was it. My deploy.restartPolicyType: configuration did not follow the schema.json preventing the service to start.


Status changed to Awaiting Railway Response Railway 12 months ago


Status changed to Solved brody 12 months ago


Railway
BOT

a year ago

🛠️ The ticket Issue with container creation has been marked as todo.


Railway
BOT

a year ago

✅ The ticket Issue with container creation has been marked as completed.


Welcome!

Sign in to your Railway account to join the conversation.

Loading...