It seems like the error you are experiencing may be attributed to some issue in the backend. I am following up with our Engineers on this to investigate further.
right now custom domain is working back again…
but we have now getting a new problem, with a 409 in templates_universal_login PUT ```
{ “statusCode”: 409, “error”: “Conflict”, “message”: “Template update conflict.”, “errorCode”: “templates_universal_login_conflict”}
Our Engineering team has informed me that the 409 errors you have been experiencing have been resolved in a recent update through the webtask and you should be able to carry on without receiving 409s for universal login.
Could you please give it a try and let me know if everything is working as expected?