GraphQL
environmentCreate
504 timeout error

timolegrosPRO

2 days ago

Hey,

I'm trying to duplicate an environment with the environmentCreate mutation. I'm using skipInitialDeploys: true to try to reduce amount of time it takes to duplicate but the request still errors out with 504 timeout meaning I don't get an environment ID as a result.

Note, the request inputs/variables are correct as the environment is eventually created (can view it on the dashboard).

Is there some kind of strategy to handle this issue?

I realize that I can "try catch" and then poll environments query to find the environment that was created by name but this seems inefficient API usage wise and I am wondering if there is a better alternative (especially given that the rate limit is 1k requests per hour)

Project ID: 7ec85ff5-87a0-4c12-80f4-67924453d491

Awaiting User Response

1 Replies

timolegrosPRO

2 days ago

It seems that this is also an issue on your dashboard. When duplicating the same environment from the dashboard it errors out in 504 and leaves the dashboard in a "dead" state.

1382001191487148300


deowkPRO

a day ago

I am running into the exact same issue


echohackEMPLOYEE

a day ago

This thread has been escalated to the Railway team.

Status changed to Awaiting Railway Response echohack 1 day ago


railway[bot]

9 hours ago

Hello!

We've escalated your issue to our engineering team.

We aim to provide an update within 1 business day.

Please reply to this thread if you have any questions!

Status changed to Awaiting User Response railway[bot] about 9 hours ago


3 hours ago

Is this still an issue?


GraphQL `environmentCreate` 504 timeout error - Railway Help Station