on
11 Apr 2025
01:51 PM
- edited on
30 Apr 2025
02:24 PM
by
Michal_Gebacki
You can see some User actions' duration exactly 180 seconds / 3 minutes.
In early 2023 Google introduced wake-up throttling that is supposed to decrease energy/battery consumption in our devices. This means the user actions "Affected" by this mechanism that we monitor with RUM, run into a timeout (the 3 minutes is a hard limit we defined).
The solution is to set vcsb=1 property in the particular RUM Application settings - > Capturing -> Custom configuration properties:
This will force Visually Complete calculation in such cases and thus prevent user actions with 180 seconds length, while Visually Complete will still be correctly calculated in standard scenarios.
If this article did not help, please open a support ticket, mention that this article was used and provide the following in the ticket:
Hi Adam,
Thanks for the great recommendation. I have over 360 apps to update, is there an API endpoint I can use to automate this?
Thanks!
Yes, of course, there is a customConfigurationProperties element under the MonitoringSettings object in our docs that can do it 👍.
Let me know if you need an example.