Publishing a single place file can often take 5+ retries which adds up significantly when publishing multiple place files for a large game. The errors vary between HTTP 400 and 500 often alternating.
Expected behavior
If something is actually wrong with my requests, the errors should be informative and not suddenly work after retrying it 5 different times with the same exact data.
Thanks for reporting. How large is your place file?
They’re between 40-60MB place files. We have a script that deploys all of them (about 12 places) when we update, because our game has a lot of places within it.
Hi Chasing,
Apologies for the issue you’re hitting. Can you please share your game ID in a DM for further analysis.
I’m unable to message you directly. I’ll share what I have here anyways:
We publish to the following games:
We experience these issues across all of these games. The published place files are near identical to what already is published. The API failures resolve themselves eventually, but often after a lot of retrying and failures.
The most common error is HTTP 400, which returns the following:
<html><body><h1>400 Bad request</h1>
Your browser sent an invalid request.
</body></html>
Headers:
{
["cache-control"] = "no-cache",
connection = "close",
["content-length"] = "90",
["content-type"] = "text/html",
}
Where getting this same error aswell
Bump…
The API is so hit-or-miss it’s insane. I tried publishing a file with almost identical size and it failed right after passing two minutes before. There were no code changes…
Similar issue as well. Unfortunate. Hoping for a fix soon
Any luck on a solution yet? Looking forward to your response…
This is still causing problems for us, can we get any indication that this is being looked into properly?
Things seem to have improved - having much more successful publishes in recent days.