A task that usually runs for a very similar RRT ( real runtime ) will show a very different ERT ( estimated run time ) when Method as set in UC_CLIENT_SETTINGS is chosen for Calculation method in the runtime page. For example, if the task usually runs for 5 minutes, but one of them goes to 25 minutes, the ERT will show something like 45 minutes and eventually will show under 5 minutes, something like this:
The peak and dip are very uncharacteristic compared to the RRT.
Release : 12.2
Component : AUTOMATION ENGINE
the spike and dip is how linear regression works. It emphasizes increases or decreases in runtime and so is not the correct ERT to use for instances like this where the runtime is usually static and every now and then goes higher or lower. It's more meant for instances where you would have many changes. Using average would probably be better in this case. To set it like this on all items, using UC_CLIENT_SETTINGS can set it for all objects with an ERT.
More info on the run time page can be found here: https://docs.automic.com/documentation/webhelp/english/AA/12.3/DOCU/12.3/Automic%20Automation%20Guides/help.htm#AWA/Objects/obj_runtime_page.htm
More info on ERT calculations can be found here: https://docs.automic.com/documentation/webhelp/english/AA/12.3/DOCU/12.3/Automic%20Automation%20Guides/help.htm#AWA/Variables/UC_CLIENT_SETTINGS/UC_CLIENT_ERT_Parameters.htm