Update set Taking longer time to commit

[Rahim2]

Hello community!

Hope everyone is doing great.

My query is when I am capturing  updates related to choice value ie "Choice list" in update set. when I move

the same update to QA it is taking more than usual time to commit successfully i.e. 20-22 mins.

I am checking total execution time in progress worker for the update set I want to commited.

What could be the reason ? need help /guidance on this.

thanks,

AbdulRahim

[Sai Kumar B]

Hi Rahim,

By default, the update set Commit is an ASYNC process and it runs in system schedulers' free time.

Sometimes when we are committing the update sets during business hours it will take more time because of more people accessing the instance. 

Generally, whenever we commit the update sets it will clear users' cache in order to reflect the new changes. If more people are accessing the instance then it will take more time.

[Rahim2]

Hello Sai,

Thanks for the reply. this is happening only if I am capturing choice list updates.

In general it takes few seconds to commit the update set but in my case its taking 20mins.

[Andy Tappa]

We had the same issue on our Tokyo instance and opened up a support case. They pointed us to KB1438109 which details the issue, problem record, as well as the intended upcoming fix version.