Error "Lock request time out period exceeded" when creating a new measure on semantic model

[charrington]

Hi guys,

We used to work with Fabric for months now on the trial.

Since this week we switched to a reserved capacity F64.

I was able to create some measure before on this same model, but now I get this message when tring to create a new one:

Underlying Error{"batchRootActivityId":"a4f162b1-b688-4eef-883a-8a9aceb14610","exceptionDataMessage":"Lock request time out period exceeded."}

One thing I find strange is in the message you see at bottom it refers to region South central US which was the region for our trial capacity. But our reserved capacity for which I am getting the error is locatd on East US2 region. But maybe it's not related, I don't know.

Haven't found anything on forums about this issue. Looks lke a bug. Really annoying...

Thanks

[charrington]

I am also seeing another weird behavior for measures, soI am adding it here as well since it might be related.
Sometimes I am able to add the measure, but when I come back to the model to see/change it, it show like this:

So I have to redo it again...little buggy.

[v-nikhilan-msft]

Hi @charrington 
At this time, we are reaching out to the internal team to get some help on this.
We will update you once we hear back from them.
Thanks.

[v-nikhilan-msft]

Hi @charrington 

Apologies for the issue you have been facing. 

This might require a deeper investigation from our engineering team about your workspace, the artifact details and the logic behind it to properly understand what might be happening. 

Please go ahead and raise a support ticket to reach our support team:

https://support.fabric.microsoft.com/support
Please provide the ticket number here as we can keep an eye on it.

Thank you.

[v-nikhilan-msft]

Hi @charrington 
Following back to check whether you got a chance to create a support ticket.
If yes please share the details here.
Thanks.

[charrington · Accepted solution]

Hi

no I didn't create a ticket, cause a this point, I cannot reproduce the issue anymore. Maybe it was just a temporary thing...I will open it if it comes back again.

thanks for your help