1. Confirm the controller is connected and monitoring has been started with Start.Nothing is detected while stopped.
2. Confirm the rule's switch is on.
3. Check whether any required condition is switched off.
4. Check whether the schedule includes the current time.
5. Confirm at least one ordinary condition exists.A rule with only sub conditions never runs.

Cause: the controller runs the settings it received at start time.

1. Click Stop.
2. Click Start again to send the new settings.

1. Raise Sustained for and Reset after.
2. Raise the confidence or threshold for the analysis.
3. Draw a detection zone to exclude traffic outside the area of interest.

1. Lower the hold time and the threshold.
2. Check that Detection FPS is not too low.If it is, brief events fall between analyses.
3. For faces, check whether Min Face Area is excluding people who are far away.

Cause: target values are compared exactly as written.

1. Select objects from the list rather than typing them.
2. Check plates for stray spaces.

1. Raise the face Threshold.
2. Enroll additional photos of both people.
3. Check that you enrolled them in the analysis of the camera that misrecognizes them.Each analysis keeps its own list, so enrolling on one camera does not affect another.

1. Check the events area to confirm the rule ran.If it did not, see "A rule does not run".
2. Check that the Grablo app is installed on the phone.
3. Check that the app is signed in with the same account.
4. Check that notifications are allowed in the phone's settings.

1. Check that the rule has a Logging action.Records are written only by rules with one.
2. If only older records are missing, check the retention setting.Records beyond the retention limit are deleted.

1. If you see Recording…, wait for saving to finish.
2. If you see No video, the file was not saved.If clips are too large, reduce the pre-event and post-event durations.

Cause: the controller cannot reach that camera.

1. Check the camera's power and network.
2. Check whether the camera's address or password changed.
3. Check that the camera is on the same network as the controller.

Cause: there are more analyses than the hardware can support.

1. Lower Detection FPS.
2. Lower Mode.QR/Barcode, OCR, and Custom Classification have no Mode, so only Detection FPS applies to them.
3. If it is still slow, delete analyses no rule uses.

Cause: cameras, integrations, and analyses are shared between rules. Deleting one leaves the rules that used it without a target, and they stop.

1. Open the stopped rule and select the target again.
2. Next time, review the list of places an item is used, shown before deletion.