Skip to main content

How to Create an Alert (Basic)

Review the basics of setting up your Guidewheel alerts

M
Written by Mitchell Grathwohl
Updated this week

Overview

Alerts in the Issues module help teams track downtime and other conditions in real time. When an alert is triggered, it automatically creates an issue that can be tagged and analyzed later. This article covers the basics of creating and configuring alerts, including conditions, schedules, and notifications.

Prerequisites

  • Admin permissions (only admins can create alerts)

  • Access to the Issues module

Step-by-Step Instructions

1. Create a New Alert

  1. Go to Issues > Alert Settings.

  2. Click New Alert.

  3. Select the devices the alert will apply to (single or multiple).

  4. Choose the condition to monitor:

    • Down: machine not running (not in green)

    • Idle: machine idle (yellow region)

    • Offline: machine offline (red region)

    • Tip: Most customers start with Down, since it captures any time the machine is not running.

2. Define Alert Rules

  1. In Create when rule is true, set how long the condition must be active before an issue is created.

    • Example: Down for 5 minutes → trigger alert.

  2. In Clear when rule is true, set how long the machine must be running before the alert clears.

    • Example: Up for 1 minute → clear alert.

3. Customize Alert Details

  1. Enter a message to display with the alert (e.g., “First shift downtime” or “Lunch break downtime”).

  2. (Optional) Auto-tag issues created by the alert with a default tag.

4. Set Up Notifications

  1. Add one or more users to receive notifications.

  2. Choose the notification method: email, text message, or both.

  3. Set notification timing (how long after the alert triggers the user is notified).

    • Example: send an email instantly, send a text after 20 minutes.

    • Notifications are additive — each user can have different delays.

5. Configure Alert Windows

  1. Go to the Alert Window section.

  2. Set the start and end times for when the alert should be active (e.g., 7:00 AM to 3:00 PM for first shift).

  3. Use the checkbox to disable a shift or All day to make the alert always active.

Tips & Best Practices

  • Avoid overlapping alerts — each alert should have a unique purpose.

  • Use clear, descriptive messages so your team knows why an alert was triggered.

  • Review your shift schedules in the alert window to ensure alerts align with operating hours.

  • Start with Down alerts before adding Idle or Offline conditions.

Troubleshooting

  • Can’t create new alerts → Confirm you have Admin permissions.

  • Alerts not appearing → Check that the alert window is active for the correct times.

  • Users not receiving notifications → Verify notification delays and confirm the correct email/phone is entered.

  • Too many duplicate issues → Review alert conditions to avoid overlap.

Did this answer your question?