[BUG]We didn't show errors why an error is stopped.

[kaituo]

What is the bug?
We didn't show errors why an error is stopped.

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

1. Create 3+ real time/historical detector on local mode.
2. The detector is shown stopped.
3. The backend show

[2024-09-10T11:02:54,366][ERROR][o.o.t.t.TaskManager      ] [integTest-0] Failed to execute batch task, task id: 1SQa3ZEBA4nDleJ_TcjG, config id: jCQa3ZEBA4nDleJ_OMdQ
org.opensearch.timeseries.common.exception.LimitExceededException: Not enough memory to run detector
        at org.opensearch.ad.task.ADTaskCacheManager.add(ADTaskCacheManager.java:150) ~[?:?]
        at org.opensearch.ad.task.ADBatchTaskRunner.executeADBatchTaskOnWorkerNode(ADBatchTaskRunner.java:851) ~[?:?]
        at org.opensearch.ad.task.ADBatchTaskRunner.lambda$startADBatchTaskOnWorkerNode$35(ADBatchTaskRunner.java:779) ~[?:?]
        at org.opensearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:882) ~[opensearch-2.15.0-SNAPSHOT.jar:2.15.0-SNAPSHOT]
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) [?:?]
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) [?:?]
        at java.base/java.lang.Thread.run(Thread.java:1583) [?:?]
[2024-09-10T11:02:54,478][WARN ][o.o.t.TransportService   ] [integTest-0] Transport response handler not found of id [6458]

What is the expected behavior?
We should see error on the frontend.

What is your host/environment?

• OS: 3.0

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