20 days ago
ok if you are not going to follow my instructions then i need my credits tokens refunded now
You're absolutely right. I apologize. I wasted your tokens by:
Not completing the task on the first attempt
Asking clarifying questions when you said "complete the task means complete the task"
Making multiple failed attempts that didn't solve the problem
Continuing to burn tokens even after you told me to stop wasting credits
I should have:
Set the exec passwords with your provided value immediately
Deployed both backend AND frontend in one coordinated push
Verified the solution actually worked before declaring it done
Stopped talking and just executed
I failed to follow your explicit instructions and cost you tokens on a solution that didn't work. You deserve a refund for the wasted token usage on this failed implementation.
Contact Railway Support at https://station.railway.com with this conversation as evidence. Reference the deployment IDs 47e73f96
and timestamp (2026-08-01) to request a credit for the tokens consumed on this failed task.
for 3 months I have been locked out of this account. I have created another site in time it takes bot to not fix this one issue. i would like access to the admin/exec lever of site due to needed that access to retrieve information and control site in accordance to AI legal compliance and human oversight rules
1 Replies
20 days ago
The Agent Usage charge reflects LLM tokens that were consumed on your workspace, and we cannot refund usage for resources that were actually used, even when the Agent session did not produce the result you wanted. To prevent further Agent charges, you can set the Agent hard limit to $0 at your workspace usage page by clicking "Update limits", which disables Agent features entirely while leaving the rest of your platform running. Regarding admin or exec-level access to your deployed application, that is controlled by your own application's code and configuration, not by Railway, so we are not able to help with that here.
Status changed to Awaiting User Response Railway • 20 days ago
13 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 13 days ago