Getting Error "Problem processing request" on Railway public API
trackingtrade
PROOP

6 months ago

Greetings,

I created a Python script to generate a database backup and then restore it to a new database (the goal is to automate the update of production data for staging).

This first part is already working correctly. My problem is that in cases where the database is very large, I need to free up more memory on my script server and the target database. So I tried to create a connection to the railway public API, following this documentation:

https://docs.railway.com/guides/manage-deployments

Where I want to retrieve the most recent deployment and then redeploy it in my script service, after the pg_dump and pg_restore steps to clear the server memory.

I created a token in my staging environment to test. However, not even a basic API connection test is working and I dont have no more details for error reason.

Connection test I performed:

curl -X POST \

https://backboard.railway.com/graphql/v2 \

-H 'Content-Type: application/json' \

-H 'Authorization: Bearer token_here' \

-d '{

"query": "query GetLatestDeployment($projectId: String!, $environmentId: String!, $serviceId: String!) { deployments( first: 1 input: { projectId: $projectId environmentId: $environmentId serviceId: $serviceId } orderBy: CREATED_AT_DESC ) { edges { node { id status staticUrl } } } }",

"variables": {

"projectId": "fdc7f7d7-9067-4503-a74d-fsdfdsf",

"environmentId": "7ffcf173-3613-4110-91ec-sfsdfds,

"serviceId": "56a59b8f-1a47-4111-a31e-esfdsfsdf"

}

}'

Error returned: {"errors":[{"message":"Problem processing request","traceId":"2041332158081415599"}]}

Could you please help me with this problem? Are you having any problems connecting to the railway public API? I believe the variables I passed are correct, I checked a few times.

Best regards.

Solved$20 Bounty

0 Replies

brody
EMPLOYEE

6 months ago

This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.

Status changed to Open brody 6 months ago


Status changed to Solved trackingtrade 6 months ago


Loading...