Sleeping (AKA serverless) shouldn't affect fresh deployments.

But something is causing problems; the last deployment was about three months ago, and after your problem, I can't upload updates.

Have you tried relinking your Github account?

What are the errors occuring during the build phase? Can you share them?

mi package.json

Can you provide the build logs? Not just the agent’s diagnosis?

Try deleting the lockfile and the modules directory, run npm i, and commit the newly generated lockfile. Also, I’d recommend running npm ci instead of npm i in your Dockerfile.

I have never directly manipulated Docker

Based on the agent's analysis, there is no package-lock.json present during the build process; this is resulting in a missing subdependency that @material-table/core relies on. So did you add package-lock.json to your .gitignore file? If yes, remove it, and push it to your repo.

Alternatively, as the agent suggested, try downloading the subdependency manually using: npm i @mui/icons-material@5.15.20

I didn't modify anything; the last successful deployment was three months ago without any issues. Today, after the railway problems, I uploaded another deployment as usual. But this time I'm having all these problems.

Based on the commit messages visible in your shared images, you did make some code changes to your repo and pushed to github. So those changes could be causing your issues. You can try the suggested solutions in this thread to fix your issue.

There were no code changes; a deployment was simply performed by uploading something new (a console.log file was added) to GitHub to trigger the deployment. This is unlike previous cases where redeploy attempts failed, always resulting in the same error.

Delete any existing lockfile that’s present in your local environment, run npm i, and commit the changes.

Let's see what happens now.

What errors are present in the logs?

I can't get him out of this state Sleeping

I’d fix whatever is wrong with jsconfig.json.

this is how it is now: {

"compilerOptions": {

// 1. Borra la línea de baseUrl

"paths": {

  // 2. Traslada la ruta relativa directamente aquí

  "@components/*": ["./src/components/*"],

  "@utils/*": ["./src/utils/*"]

}

}

}

This is how it was before: {

"compilerOptions": {

  "baseUrl": "."

},

"include": ["src"]

}

You can’t have comments in a json file.

{

"compilerOptions": {

"paths": {

  "@components/*": ["./src/components/*"],

  "@utils/*": ["./src/utils/*"]

}

}

}

This is how it should be.

??????????

what does the error says now?

consulta solicita que fuera privado el ticket de ayuda, porque hay personas que no son de Railway?

Please keep things in English.

The inquiry requests that the help ticket be made private, because there are people who are not from Railway?

Is there a lockfile present in your repository?

Not that I know

Unfortunately, so far, this isn’t a Railway issue, and there aren’t any sensitive information in the thread. A team member will not be assigned to this thread.

Can you run npm i locally and commit the generated lockfile?

I actually upload the deployment from my code to GitHub and from there to Railway. I already tried deleting the package.look file and running npm i again.

Are you using Nixpacks?

I tried both Nix and the recommended railway.

Try using a Dockerfile. Make sure to copy both package.json and package-lock.json and run npm ci instead of npm i.

My question is, if I didn't modify anything in my code and neither did GitHub, why did the application freeze like this? As I mentioned, I never use direct commands in the console. I always use deploy or reload from the dashboard.

Dependencies can get updated, and as a result, cause this error. A lockfile locks the version of these dependencies.

Okay, but I don't know how to do what you're suggesting, and I don't want to change something I won't know how to undo later. Isn't there another way?

I’m highly recommending you to use a Dockerfile or a Railpack config file so you can control how the build process is done. You can always revert the changes in Github.

I understand what you're saying. But I've never directly intervened in Docker. Can you bring it out of sleeping mode?

You can try restarting the deployment by clicking on the 3 dots.

gives the same result

Try clicking redeploy then.

ok

?

Issues two and three are the original problem within the package.json file. I have version 0.2.37 declared because I specifically need that version, and as you can see, the version number isn't highlighted. The same applies to @mui/material@5.15.20, which isn't in the package.json file.