We have been building and updating a BabylonJS application for the last two months. My team and I were last able to successfully update our Javascript code last Wednesday 15th of May, the build was working fine and the page was updated well. I was actually able to update two pages.
We are attempting to update the codebase of the online store through shopifies code editor and the edit code button.
Since then we are receiving errors when trying to upload the same code to those pages, or small JS updates to those pages. We are receiving 503 error from our PUT request that stipulates that the Service is Unavailable and we should try again in a few minutes.
If you’ve an idea of what we are doing wrong please let us know!
1 Like
Hey @Dev_Alden 
This does definitely look odd, are you still seeing the issue pop up (just wondering if it was intermittent)?
If so, could you try replicating the 503 error with Chrome DevTools open like you had before, but check the network tab for the error response and share the X-Request-ID header that you should be able to scrape from that tab from the failed request. I can use that to investigate further on our end here.
One other thing you could try would be updating your theme using the Shopify CLI as an alternative method if you are familiar with it, which might bypass any issues with the web editor. Also, could you let me know the approximate file size of the file you’re trying to update? I can’t say for sure, but I’m wondering if that could potentially impact the upload.
Hope to hear from you soon - let me know if I can clarify anything on my end here.
Hello @Alan_G
This error is still occurring, I would like to note that we are in contact with the shopify Technical Merchant Support, and they are currently looking into this issue, I have sent them a screen share as well as the HAR files.
I have replicated this error on a separate theme/ website so that I didn’t ruin what currently we have up!
Here is the requested header:
x-request-id
4923fe63-4acd-4b11-ad3f-e1ad556c429d-1747816695
My colleague has been testing out the CLI and updating the asset from there, it seems to be working on that front, so we will probably migrate to using that in the future.
As for the size of the file it is 6.1 mb which should be within the file size limit.
Cheers
Devs from Alden
Thanks @Dev_Alden - appreciate you grabbing that request ID and thanks for the file size details as well. I’ll do some more digging into this and loop back with you as soon as I have more info on my end here 
Hey @Dev_Alden - just following up here. This was an issue on our end - a fix is in the works. Can’t guarantee a turnaround time, but just wanted to update you on progress - I’ll update you again once I can confirm this has been fully resolved.
Hey @Alan_G
Thanks for following up here!
We’ve managed to go through the CLI so thank you for letting us know about that route!
Even so, let us know once the issue is resolved 
Cheers
Devs at Alden
No worries @Dev_Alden, glad to hear the CLI workaround works for you - I can’t share too much internal info, but I can confirm there is a fix in the works now for the issue within the theme editor itself though. I’ll update you in this thread here once I can confirm it’s deployed (just in case anyone else comes across this thread in the future) - thanks again for flagging this
Hi,
The fix for this should be available - so you should be able to use the editor as expected now.
1 Like
Dear @Liam-Shopify && @Alan_G
Thank you so much!
Kind Regards
Devs at Alden
1 Like
