Sebastian Wiszowaty

No idea how to replicate this, only have this in a single environment in production and can't remediate it.

Did you even read the issue? It just happened. No way to resolve this issue. No replication steps available. It should never happen ergo it's a bug.

Just because something does not have replication steps does not mean that it's not a bug. This incident just proves that the issue is inside of the workspace and had...

Let me know if you need to have the sub/la/rg ids - I'll be able to provide them on Monday - [email protected]

Just to confirm, when the original 'ETM' WL is removed, the latter is still there. CLI does not show that it's there - ergo can't delete it - can't fix...

Any update, this is causing issues in production environment for a couple of weeks now...

@v-muuppugund Is there any update on this - the issue is still causing issues in our production environment and causing additional work for our agents.

@v-muuppugund Any update?

@v-muuppugund Any update?

How can this be closed if the issue is live in the current environment and I'm unable to fix it?