Sleepy Server; 504 Gateway Timeout

Tags: #<Tag:0x00007f820bb075e0> #<Tag:0x00007f820bb07388> #<Tag:0x00007f820bb07158> #<Tag:0x00007f820bb06f00> #<Tag:0x00007f820bb06cf8> #<Tag:0x00007f820bb06bb8>

Hi there,
I’ve tried to add a great bunch of releationships for this classical 4 disc release:

When submitting I get an error message:

Any idea how I could save my work? I don’t want to loose the work of half a day :cold_sweat: :crazy_face:
Any workaround appreciated…



PS this isn’t the first time I recognize this. Before I could submit my edits anyway after waiting a short time. But today not, tried 4 times

1 Like

I got something similar recently when trying to add a small number of ‘parts’ relationships to a very large series (BWV). I was only able to do it the other way round (adding ‘part of’ relationships to the individual entities). I don’t know how to save state in a situation like this but would also be interested if there is a way. Also, maybe the timeout is too short?


It’s unfortunately due to the current load issue on our database server. Large requests are impacted first. We are working on improving the situation by isolating services and changing load balancer. Nonetheless, it is not recommended to keep an editing form open for half a day, not only because of load issue, but also because other editors might change the data you are working with in the meantime. Thus a workaround is to submit more smaller sets of modifications, which have another advantage: edit notes can be made more specific.


In this example, I was guilty of something myself. It became more complex and elaborate than expected. I’m relatively new to this classical area and had to read much documentation and HowTos in parallel. Time consuming… Then I had to interrupt because of an appointment and could first continue (much, too much) later…

Is there any hint as to which time limits, number of relationships or for which kind of relationships this becomes particularly critical? Then I could consider that in the future.

By the way: In the meantime I had to reboot my computer due to an other problem and all is lost anyway :confused:


Just trying to update a 64 disc release, unsuccessfully.
Your suggested workaround should be applied at MusicBrainz not the user level!
The problem is that none of the update requests are processed (or have been backed out).
Track level updates need to be applied in track by track order so that if a timeout threat is looming then after a certain number of updates have occurred (eg. end of medium or 100? tracks updated) the user screen is updated accordingly with the ticks removed from those track selection boxes (and an incomplete message displayed). This will enable enter to be pressed for a new update request.