Similar thread from 2 days ago:

https://station.railway.com/community/can-t-view-deploy-or-http-logs-in-the-ne-729821a9

Gaslighting customers and failing to render services as part of contractual obligation is disrespectful and constitutes grounds for breach of contract.

I shared the information of the prior context and I'll keep my language pg-13 from now on but you need to fix your broken platform and broken web ui.

Finally I should be able to use railway logs to access the logs instead of a complete failure of the command.

This expectation comes from the documentation at https://docs.railway.com/observability/logs

https://res.cloudinary.com/railway/image/upload/v1694195563/docs/CleanShot%5F2023-09-08%5Fat%5F10.52.12%5F2x%5Fyv1d7f.png

the prior employee was less than helpful and denied the problem existed instead of viewing the screenshots and screencasts.

I just want the logs to work again and for actions in browser tab A to be encapsulated to browser tab A.

This ui update is half baked. Even the AI agent itself said:

"The HTTP logs tool is broken on the backend right now—it's returning validation errors.

Your best option is the deployment logs I just pulled, which show all requests and responses. That's the live traffic data.

If you need something specific from HTTP logs (like filtering by status code, path, or method), I can search the deployment logs with those filters instead. What are you trying to find?"

Prior Context

(see attached priorcontext.png as well as the attachments)