Darek Szatkowski

I've set up a new solution on v10, again using Redis cache, and experienced the same issue on the subscriber web app which is scaled up to 3 instances. This...

Hmm, I can't reproduce this issue any more after removing the Redis cache conn string. I'll try again tomorrow.

Ah, you're right. I forgot that the whole app service plan is scaled out and not just the web app. My mistake. I made a PR where I specified this...

I've also encountered it twice on Umbraco Cloud projects for around 4 different users. I can't reproduce it, though :( Same exact error and version of the CMS as you....

This is what I did to get rid of these users since I could delete them via the backoffice: 1. Go to the [umbracoUser] and find the id​ of the...

Hi @romeguarin It's not, as Heartcore is a SaaS product. Also, please note that the recommended workflow on UC is dev>stage>live and we don't support restoring schemas in the opposite...

I agree that it's not ideal for you to recreate dev, nor should you do that. My recommendation would be to either teach the recommended workflow to anybody with access...

@romeguarin something must have gone wrong in the env creation/deletion process. There's no reason for me not to recommend you the best solution I can provide you with and I'm...

reinstalling [WSL](https://learn.microsoft.com/en-us/windows/wsl/install) fixed it for me

I've recorded this exact same error a bit over 2 months ago when I was testing UmbracoID locally with the internet turned off. Here's the video I've recorded back then...