Closed katjam closed 5 months ago
@AutumnBarlow I made this issue to note anything I find out.
OK. It looks like it is something with Azure.
I remember looking at this with Tim. We had to manually delete some of the staging environments in the Azure control panel. I don't remember why they get created but I think we decided it was a reasonable work-around to manually remove them when they built up. I've cc'd Tim to shed some light. I'm not sure if I have access to the Azure environment so I'll wait to hear if you need me.
Closed. WT have turned off deploy of previews to Azure
Secondly – do you know of any updates lately to Netlify? It was working fine earlier this week when Joe uploaded some new content about compost (it’s wall to wall excitement here at the Wildlife Trusts). But today neither of us can move forward on editing and publishing some new content because the save button no longer responds. We’ve spotted some new features like the preview button (which previews the whole site rather than the content being worked on) so I wonder if there have been some general changes?
I can see from GitHub some steps are failing:
As it’s saying Azure, is this a problem with the way we interface with Netlify? I have no idea what I’m talking about – if it’s a problem with our end/Azure, I’ll get in touch with Tim here.
If it’s not us, should I raise a ticket through GitHub?