Confusion about linking App vs Linking Service

[wide roost]

Last night @fluid sage fixed a 500 ("We'sorry, but something went wrong") error on my app that was due to a disconnect between my app and my database ostensibly because my railway up was linked to my Postgres service instead of my website service. I was very happy to get that help.

Today, I deployed a new version of the app and it appeared to deploy the app, but I again started getting the same error. I was going to re-deploy the database from the Database Service-> CMD+K->Deploy latest, but the dashboard shows that the database was redeployed in the time frame of my railway up, but the app shows as not having been deployed in two months. I have not moved forward to re-deploy either yet as I want to understand what is wrong with my console environment.

The output of my railway up sure looks like it is building the app and not the database. Am I misunderstanding something about the linking mechanism?

I have attached a screenshot of an excerpt of my console output from what I think is the app deploy.

What am I doing wrong here? I feel like I am not understanding something basic and it is keeping me from being able to troubleshoot this.

Thanks.

[fluid sage]

You linked to Postgres again and ran railway up against it.

Railway is going to try to do what you asked it to, deploy your code, there are no guardrails that prevent you from doing this.

[wide roost]

Thanks. Now I understand.

Hang on, maybe I don't understand.

After I unlink the service, railway up prompts me for a service and since I assume I do not want Postgres, I chose Motley Tones App. Subsequently, I get an error sending request failure.

11213$ railway status
Project: Motley Tones App
Environment: production
Service: None
-- tarsa@m1nomad:~/src/self/motleytones [main] --
11214$ railway up
> Select a service Motleytones
  Indexed                                                                                                                                     Compressed [====================] 100%                                                                                                    error sending request for url (https://backboard.railway.com/project/4368befc-175f-411e-aed7-9ba5a0f17748/environment/f687d285-aa1b-401c-af60-9fe36b677c40/up?serviceId=60da7e1a-3347-4840-bf54-6e94d602f4de)

Caused by:
    operation timed out

[fluid sage]

Run the command with the --verbose flag please?

[wide roost]

I do not know what changed since a few minutes ago, but the railway up --verbose appears to be working properly now.

Here is a screenshot, for the record.