Overview:
Guidewheel uses alerts to identify when a machine stops running. When these alert conditions are met, an issue is automatically created. This article helps you understand how the two concepts work together so you can better manage downtime tracking.
What is an Alert?
An alert is a rule or condition you define in Guidewheel.
Example: If a machine drops below the idle threshold for more than 2 minutes during first shift.
What is an Issue?
An issue is an actual event that occurred when the alert condition was met.
Issues appear on both the Uptime Page and the Issues Page.
How They Work Together:
You set up an alert (e.g., for downtime longer than 2 minutes).
If a machine matches that condition, Guidewheel creates an issue.
You can then tag that issue with a downtime code, assign it to someone, and mark it resolved.
Tips & Best Practices:
Use alerts to trigger only during staffed shifts so you avoid unnecessary noise.
Keep alert logic simple at first—then expand based on what you learn from the Issues Page.
Troubleshooting:
If you’re not seeing issues populate, verify that:
The alert is active and has the correct time window.
Thresholds are properly configured.
The machine actually dropped below the idle threshold during the alert window.