Versions (relevant - OpenSearch/Dashboard/Server OS/Browser): 2.15.0
Describe the issue: While running anomaly detection jobs, we often see the anomaly occurrence times not matching with interval boundaries. I thought that the occurrence should match with the end of the window as anomaly detection would be evaluating the whole bucket. Any explanation to this? Also the occurrence times seem to be independent of the configured window delay.
Configuration:
Relevant Logs or Screenshots:
