Archiving of CMDB table is based on the sys_created_on, making the archiving sooner than expected. - Known Error

Archiving of CMDB table is based on the sys_created_on, making the archiving sooner than expected. Description Archiving of CMDB table is based on the sys_created_on, making the archiving sooner than expected.

Found that the sys_auto_flush table for below tables

Archives based on "install_status=100 (absent)" with sys_created_on is older than 3600 seconds ################################################ cmdb_ci_docker_container, cmdb_ci_kubernetes_component ################################################ Archives based on "install_status=100(absent) with sys_created_on is older than 2.592.000 seconds ################################################ cmdb_ci_ip_address, cmdb_ci_network_adapter ################################################ The above setting is making the CI to be archived without giving time for the CMDB admins to react for any discovery errors.

Steps to Reproduce

Hop onto the instance Check the sys_auto_flush table for the CMDB tables check the "matchfield" column Observe the matchfield for few of the tables is based on sys_created_on Workaround * Please update the matchfield column on the "sys_auto_flush" from sys_created_on to sys_updated_on.