Ramon, the original poster of this thread (who we’ve been talking with on another ticket) mentioned that we hadn’t posted anything here about what’s going on - quite right to call us out. Thank you.
We’ve been dealing with this since over the weekend now and blank logs continue to plague us across services. We have a new reworked logging solution waiting to replace the present one which will be much more reliable and robust but at the moment we’re fighting fires with the old one.
Right now, we’re fully aware of the issue and are working as hard as we can to resolve it - failed deploys without logs are absolutely terrible!
Thank you for your patience here!
John B