renaming to 'going to run' instead of executing because when task man…

…ager exits because of api key error it won't write the error status so the actual status is 'going to run' on the next interval. This is more accurate than being stuck on 'executing' because of an error we don't control and can't write a status for.

x-pack/legacy/plugins/siem/server/lib/detection_engine/signals/signal_rule_alert_type.ts

@@ -96,7 +96,7 @@ export const signalRulesAlertType = ({
         >(ruleStatusSavedObjectType, {
           alertId, // do a search for this id.
           statusDate: date,
-          status: 'executing',
+          status: 'going to run',
           lastFailureAt: null,
           lastSuccessAt: null,
           lastFailureMessage: null,
@@ -106,7 +106,7 @@ export const signalRulesAlertType = ({
         // update 0th to executing.
         currentStatusSavedObject = ruleStatusSavedObjects.saved_objects[0];
         const sDate = new Date().toISOString();
-        currentStatusSavedObject.attributes.status = 'executing';
+        currentStatusSavedObject.attributes.status = 'going to run';
         currentStatusSavedObject.attributes.statusDate = sDate;
         await services.savedObjectsClient.update(
           ruleStatusSavedObjectType,