[BUG] Wrong real time state after executing historical run 2.15.0.0

[eruditesv]

What is the bug?
In list of detectors the real time state of detector shows as stopped after historical run is executed.

How can one reproduce the bug?
Steps to reproduce the behavior:

1. Go OpenSearch dashboards. Open left pane, go to Anomaly detection section
2. Create detectors if not already available
3. Once detector is running go to detector switch to historical analysis tab, run historical analysis.
4. Come back to list of detectors. In list of detectors the detector for which historical run was executed will have real time state as stopped.
5. If you go to the detector the state is running.
6. You will need to stop and again start detector by going to detector in order to get correct real time state in list of detectors.

What is the expected behavior?
The real time state should be running in the list of detectors.

What is your host/environment?

• OS: MAC
• Version 2.15.0.0
• Plugins Anomaly Detection

Do you have any screenshots?

Do you have any additional context?
Add any other context about the problem.

[kaituo]

I should have fixed the bug in 2.17. Can you try to upgrade?

[eruditesv]

Hi Kaituo,
Thanks for taking a look into it. Can you point me to the commit or fix for it. Is it possible to merge back only this fix to 2.15.

[kaituo]

This is the fix: opensearch-project/anomaly-detection#1287

We don't have upcoming 2.15 patch release. Are you hosting opensearch by your own or using our managed service?