Resolving Notifications

When a steam trap notification fires, your team inspects the trap and acts on it. Resolution closes the notification, records what you found, and prevents the platform from re-alerting for the same event. It is also the mechanism for building a maintenance record — inspection date, whether the failure was confirmed, whether the trap was replaced — all attached to the notification.

When to Resolve

Resolve a notification after you have done one of the following:

• Inspected the trap and determined no action was needed (false positive, upstream shutdown, known condition)
• Repaired the trap
• Replaced the trap

Do not leave notifications open indefinitely. Open notifications obscure the true state of your fleet and count against your unresolved alert totals in the dashboard.

Which Notification Types Use This Form

The inspect-and-replace resolution form applies to trap failure notifications:

• Blowthrough
• Intermittent Blowthrough
• Leaking By
• Unexpected Cold (Failed Cold)

Sensor status notifications (Offline, Sleep, Service Needed) and steam on/off notifications have separate resolution flows and different fields.

Where to Resolve

From the Notifications page: Open Shoplogix IMS, navigate to Notifications, and find the open notification. Click the notification to open the detail view, then click Resolve.

From the trap detail page: Navigate directly to the steam trap. Open notifications for that trap are shown on the detail page. Click Resolve next to the relevant notification.

Both paths lead to the same resolution form.

Resolution Workflow

1. Open the notification and review the event details — trap identity, sensor MAC address, event timestamp, and notification type.

2. Choose what happened during your inspection:

   Trap inspected? — Toggle this on if you physically examined the trap.

   • Enter the Inspection Date.
   • Indicate whether the status was confirmed (yes or no). Selecting "no" means you inspected the trap and did not find it in the reported failure state — this records the outcome as a false alarm or a condition that had already self-resolved.

   Repaired or replaced? — Toggle this on if the trap was serviced.

   • Enter the Replacement Date.

3. Add any notes about what you found, the conditions at inspection, or any follow-up needed. Notes are stored on the notification record and visible in history and via the API.

4. Click Resolve to submit. The notification moves to Resolved status.

Important: For Blowthrough, Intermittent Blowthrough, and Leaking By notifications, if you confirm the failure (Status Confirmed: yes), the trap must be marked as replaced to enable the Resolve button. This enforces the expectation that confirmed blown-through or leaking traps are physically addressed before the notification is closed.

After Resolution

• Monitoring continues. The trap remains under active sensor monitoring. If the same failure condition recurs, the platform generates a new notification.
• History is preserved. Resolved notifications remain in the Notifications page history. Use the status filter to toggle between open and resolved views.
• Resolution data is attached. Inspection date, replacement date, event confirmation, and notes are stored on the notification record. These fields are accessible via the API and inform maintenance reports.

Permissions

The Customer User role and above can resolve steam trap notifications. Read-Only users can view notification history but cannot submit a resolution.

Bulk Resolution

Bulk resolution is not supported. Each notification must be resolved individually. This is intentional — the resolution form captures inspection-specific data (dates, confirmation, notes) that cannot be applied meaningfully in bulk.

API

POST /v2020-07/steamtraps/{trapId}/notifications/{notificationId}/resolve

Request body (SteamTrapNotificationResolution):

Field	Type	Description
inspected	boolean	Whether the trap was physically inspected.
inspectionTimestamp	int64 (unix seconds)	When the inspection occurred.
eventConfirmed	boolean	Whether the failure event was confirmed during inspection.
replaced	boolean	Whether the trap was replaced.
replacementTimestamp	int64 (unix seconds)	When the replacement occurred.
notes	string	Free-form notes about the resolution.

All fields are optional, but at minimum inspected or replaced should be set to make the resolution meaningful. The response returns the updated notification object.

Related

• Unexpected Cold Events — for guidance on investigating and responding to Unexpected Cold notifications specifically
• Ground Truth — for recording a physical measurement at inspection time to correlate with sensor data