"API call to Engine service was not successful: Failed to get app 'StaticByteSize'."

[Skage]

The Repository log is full of "API call to Engine service was not successful: Failed to get app 'StaticByteSize'." errors. Several 100 per day and server.

This is the stacktrace:

Spoiler

at Repository.Core.Repository.Common.AbstractModelRepository.CheckConflicts(IRepositoryObject persistedItem, DateTime itemModifiedDate)↵↓ at Repository.Core.Repository.Common.ModelRepository`1.UpdateMany(IEnumerable`1 items, Boolean appendPrivileges, Int64 privilegesFilter)↵↓ at Repository.Core.Repository.Common.ModelRepository`1.Update(T item, Boolean appendPrivileges, Int64 privilegesFilter)↵↓ at Repository.Core.Repository.Common.SecurityAwareRepository.RunWithElevatedOrNoSecurity[TResult](Func`1 func)↵↓ at Qlik.Sense.Common.Ioc.WorkScope.Work[T](Action`1 action)↵↓ at Repository.Communication.Clients.EngineClient.UpdateAppStaticByteSize(App app, Int64 appStaticByteSize)↵↓ at Repository.Communication.Clients.EngineClient.GetAppStaticByteSize(App app)

This is a multi node cluster running May 2024 Patch 10. PostgreSQL is unbundled with the Qlik PostgreSQL Installer.

One of the suggestion is to disable the StaticByteSize-lookup all together but that is not a very attractive "solution".

Does anyone know what we can do to solve this?

TIA!

/lars

[Alan_Slaughter]

Hi Skage, please give this article a try:

https://community.qlik.com/t5/Official-Support-Articles/How-to-disable-Base-memory-size-info-and-Sta...

[Skage]

Hi @Alan_Slaughter 

I looked into this article before submitting but as I wrote - that's not an attractive "solution". But it seems like I have to.

So the "solution" to a feature, that doesn't seem to be well designed, is to disable it? Should it even have been delivered and enabled in the first place? 

How did this get passed QA?

/lars