SecurityInsight settings · Settings > Guards
Daily flow: job did not start
| Key | SI_Guard_FlowStepStartFailed_Enabled |
|---|---|
| Where | Settings > Guards (safety checks) > Other checks |
| Type | On / off |
| Default | Off |
| Edition | Community |
| Confirmation | SecurityInsight asks you to confirm before it is switched off. |
What it does
The safety check that protects the jobs of the daily flow: A job in the daily flow could not start: its container stopped before SecurityInsight ran (an Azure platform problem).
When enabled
the check works as described on the Guards page.
When disabled
no event and no mail; a job that does not start is still not run.
Risk and how to reverse it
Turning this check off removes a protection: when its condition happens, nothing holds or stops the step and no event is raised. Reversible at once: switch it back on; it applies from the next run.
Requires
Works only while "All guards (safety checks)" is on.
Recommended
Keep the default (off) unless you want this check to hold or stop the step. Change it when: Off by default: only the two brakes stay on (CIs retired by mistake, duplicate vulnerability records) -- this check is a warning you can switch on. Turn it on when you want it to hold or stop the step, and mail, again.
Documented for SecurityInsight 3.0.79. Written by the SecurityInsight team; Invardia publishes it. · All settings · Security review pack