2 months 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
2 Replies
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.
2 months ago
I am running into the exact same issue
2 months ago
This thread has been escalated to the Railway team.
Status changed to Awaiting Railway Response echohack • about 2 months ago
2 months 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 • about 2 months ago
2 months ago
Is this still an issue?
2 months ago
can you please share more information. what mutation with the API are you making. what is the response in the network tab (like from the screenshot)
2 months ago
🛠️ The internal ticket Error duplicating environments through dashboard and public API has been marked as in progress.
10 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 • 10 days ago