Troubleshoot alert behaviour - OnSight Knowledgebase

Troubleshoot alert behaviour

Back to Troubleshooting & support Browse product

Use this guide when an alert did not fire, fired unexpectedly, or was recorded in Command but did not reach the expected person or external system.

Start with the alert record and the source data. An alert is only as accurate as the sensor reading, device status or zone activity that caused it.

If an alert did not fire

  1. Open the affected asset and confirm the expected hardware is linked and sending data.
  2. Review the asset's current and historic sensor readings for the time in question.
  3. Open the alert and check that it applies to the correct asset, sensor or condition.
  4. Check the threshold and breach timing. The reading must meet the configured condition for the required duration before the alert can trigger.
  5. If the alert is associated with a job, check that the job was active. A job applies its alerting profile while it is running and removes it when the job ends.
  6. For gateway offline alerts, confirm that offline alerting is enabled on that gateway. It triggers when the gateway has not reported for five minutes.

See Create an alert and Run a job.

If an alert fired unexpectedly

  1. Review the readings, status changes or zone activity at the alert time.
  2. Check whether the source data genuinely met the rule. A short spike, a device going out of range, or an inferred zone departure may explain the event.
  3. If the event was valid but the rule is too sensitive, adjust the threshold or breach duration.
  4. If the event should remain recorded but fewer people need to receive it, adjust the notification settings instead.
  5. Keep compliance-critical alert rules deliberate: record why you changed them and confirm the new setting matches your operational requirement.

If people did not receive the alert

  1. Confirm the alert actually triggered in Command.
  2. Ask the affected user to check their individual alert-notification preference. Users can disable alerts for themselves.
  3. A Company Admin can review or change a user's notification preference on their behalf.
  4. Check the recipient's email address and normal mail filtering, including junk or quarantine folders.
  5. If you use the optional WhatsApp add-on, confirm it is configured for your company.
  6. If you use a webhook, check that the breach or recovery URL is correct and that the receiving system can accept the POST request.

Alerts can be delivered by email, webhook, or the WhatsApp add-on where enabled. See Manage alert notifications.

If a WhatsApp alert link contains {{1}}

A WhatsApp button link that contains the text {{1}} immediately before the alert ID is automatically corrected when Command opens it. Sign in if prompted; Command will then take you to the intended alert record.

If the alert does not open after signing in, contact your reseller or OnSight and include the full link and the time you received it.

Escalate with evidence

If the outcome still cannot be explained, contact your reseller if you have one; otherwise contact OnSight directly. Include the asset and alert name, relevant sensor readings, timestamps, the configured condition and duration, whether the alert appears in Command, and the notification channel being investigated.

More in this category

Related guides for this topic.

Need a hand?

Tell us which product you use, what you’re trying to do, and what happened.

Contact support