I managed to catch this while the error was occurring and I can confirm that it is an issue with the Shells not the Global colours.
The global colours are present in the styles in the frontend, the Shells are not present and that is what causes the issue.
I also confirm it happens seemingly randomly after editing a post - there may be something specific about certain posts that cause it but I haven’t isolated what that is.
Just following up with this, we are having to check the site daily to catch this.
It is getting to the point where we are considering removing the tailwind parts that are being affected as that will require less work than continuously monitoring and re-saving the global colours.
I’m sorry to hear you’re still having trouble with this.
Are you having to check when no changes are being made to the installation?
I was not able to reproduce this on my end in the previous tests, but will create a sandbox installation with multiple scenarios for you to see if you can reproduce.
We are having to check daily because we don’t know when the client will be editing the site pages or posts.
This happens randomly and can happen after any edit they do and we don’t currently have in place an automated way to notify us after they have made an edit.
Unfortunately I can’t be any more specific than I have. It happens intermittently and we do not know the specific cause other than it happens because of post editing.
The best I can do is replicate the environment in a staging site and give you access.