As we can see from the status page, the Groovy platform is still in bad shape. This has the potential to affect anything using the platform – webCoRE, other smart apps, device handlers, anything that runs off-hub and/or reports to the cloud. Personally I don’t think it’s worth spending time to find workarounds since even the simplest automations could fail due to everyone’s automations failing and attempting recovery. All of those actions are vying for limited compute power on the cloud platform, so there may be no logical patterns to be found in the failures.
This is a storm and it will blow over eventually. One would hope that SmartThings is still willing and able to temporarily autoscale the Groovy platform to deal with activity spikes following outages, but that is probably a financial decision at this point, mostly out of the hands of the ST tech team.
If anyone wants to “do their part” in helping it pass more quickly, the best thing we can do is disable our non-essential high-overhead automations. If a piston is running every minute and doesn’t really need to, consider disabling it until the storm passes. We all have the opportunity to slightly relieve the platform load.