I would look into what you have done differently this time around, that is a clear indication that something was previously miss-configured.

Well at first I was just trying to hit my backend endpoint and it was taking 30+ seconds so it was failing.

My current fix now is I setup a (duplicate just the backend) new project with just the django backend everything the same as the one failing.

Duplicate is working.
So my question is do I have to just leave it as a separate project?

I would recommend you keep it in the same project.

https://docs.railway.com/overview/best-practices#deploying-related-services-into-the-same-project

I tried variable reference and it's still the same. I think the problem is that the backend on my project is getting slow. That's why when I duplicated that backend outside my project it's working fine because it's the only service in that project. Are you able to see my project on your end?

I am, and I can assure you that each service can use the resources your plan allows for regardless of what project they are deployed into.

I would add more verbose logging into your app so you can find out what part of your code is causing the delays.

Rest assured this is not a platform issue.

Yep I know, however I just don't know the reason why the primary backend is acting up.

It's working fine now using the duplicated backend