Bounds Setting's configuration to override learned control bounds in anomaly detection will not take effect immediatelySummaryAccording to documentation: https://docs.servicenow.com/bundle/quebec-it-operations-management/page/product/event-management/task/override-metric-bounds.html , you can specify custom upper and lower metric bounds to override learned control bounds in Operational Intelligence (OI) metric.This is normally performed if you want to avoid too many anomaly alerts generated in your instance.However, after setting the bounds, you will notice that anomaly alerts are still being generated. In the Insight Explorer for the metric, you can still see the old upper and lower bound. The reason is that scheduled job "Operational Intelligence - Metric Learner job" is normally configured to run daily at a certain hour. This job will recalculate the OI metric based on the new bound setting's configuration.To find out if the OI metric of certain CI has been updated properly, you can query the table sa_time_series. Normally, using the CI as filter, you should find that classifier "SKEWED_NOISY" record (this is the model that using static bound) is updated around the same time as the Metric Learner job's run. Only then: 1) the metric display in Insight Explorer will show the new upper and lower bound; and 2) anomaly alerts only triggered according to the new bound setting. Note: you might encounter a situation where not all CIs have the new bound setting's configuration after you run the Metric Learner job.Reason: Metric Learner Job will trigger the application service to rebuild the model and stored the result in sa_time_series table with "Updated" column as the date it completed the rebuilding.By design, this application service will divide the metrices in sa_metric_map table into 7 parts and will only process 6 parts per day. The 1 part that is left earlier will be processed the next day based on "6 out of 7" pattern.So, to speed-up the process, the best way would be: run Metric Learner job manually right after the change. Then, the next day, daily job will run to apply it to all CIs.