> For the complete documentation index, see [llms.txt](https://docs.didge.io/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didge.io/home/foodcore-sensors/end-user/core-functions/alerts-and-actions.md).

# Alerts & Actions

### 1. Overview

**Corrective Actions** are a critical part of the temperature monitoring system, designed to document and guide responses when temperature sensors detect readings outside set tolerances. This ensures food safety compliance and provides a robust audit trail of remedial actions taken.

<figure><img src="https://2675140142-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPnSdrHOYeIaTHbt8Z0Qc%2Fuploads%2FNqsNsPnDD3Vs7kml6qZV%2FScreenshot%202025-04-18%20at%202.15.40%E2%80%AFpm.png?alt=media&amp;token=5939ffc8-139d-4da9-86c3-9f700a30078f" alt=""><figcaption></figcaption></figure>

***

<figure><img src="https://2675140142-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPnSdrHOYeIaTHbt8Z0Qc%2Fuploads%2F341vYTtVAr1uNSmVZeuM%2FScreenshot%202025-04-18%20at%202.15.53%E2%80%AFpm.png?alt=media&amp;token=66a4838e-a382-4339-9354-437cb1cafb58" alt=""><figcaption></figcaption></figure>

### 2. How Alerts Work

Each sensor is configured with two key parameters:

* **Temperature Tolerance**: For example, 5°C
* **Delay Threshold**: For example, 2 hours

#### Alarm Conditions

An alarm is only triggered if the sensor temperature:

* Exceeds the tolerance (e.g., >5°C)
* Persists beyond the configured delay (e.g., 2 hours)

This prevents false positives caused by normal operational fluctuations like:

* Busy service periods
* Fridge restocking
* Cleaning cycles

#### Notifications

When triggered, the system sends:

* **Email alerts**
* **WhatsApp alerts**
* Each includes a **link to the active corrective action** for that alert

***

<figure><img src="https://2675140142-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPnSdrHOYeIaTHbt8Z0Qc%2Fuploads%2F341vYTtVAr1uNSmVZeuM%2FScreenshot%202025-04-18%20at%202.15.53%E2%80%AFpm.png?alt=media&amp;token=66a4838e-a382-4339-9354-437cb1cafb58" alt=""><figcaption></figcaption></figure>

### 3. Corrective Action Lifecycle

#### 1. **Auto-Generated by System**

* One corrective action is created per sensor breach
* The data updates in real time with the latest temperature value until resolved

#### 2. **User Review & Update**

* Users are expected to:
  * Review the corrective action
  * Respond with their resolution or plan
  * Submit the form to close out the action

#### 3. **Submission Logging**

* All submissions are logged as operational records
* Included in performance and compliance reporting

<figure><img src="https://2675140142-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPnSdrHOYeIaTHbt8Z0Qc%2Fuploads%2FLKZDFyqC8E2cfB4qb5wt%2FScreenshot%202025-04-18%20at%202.18.25%E2%80%AFpm.png?alt=media&amp;token=06cf47e1-cf39-4ab5-8260-8aea529b505d" alt=""><figcaption></figcaption></figure>

***

### 4. Accessing Corrective Actions

#### From Sensor Dashboard:

* Click the **Corrective Actions** tab
* Displays a table with:
  * **Date**
  * **Current Temperature**
  * **Device ID**
  * **Storage Type Tag** (e.g., Cold/Frozen)
  * **Interaction Button** to open the detailed action form

#### From Operational Work Areas:

* Lists corrective actions in **card view**
* Shows **active alerts** per area (e.g., kitchen zone)
* Quick visual reference to prioritize responses

***

### 5. Corrective Action Detail View

#### Information Displayed:

* **Unit Name, Tag, Device ID**
* **Current Temperature** and Timestamp
* **Historical Temperatures**
* **Alert Message** with cause

#### User Actions:

* Add corrective measures (e.g., "Close door and check in 30 mins")
* Acknowledge actions (e.g., "Transferred food to another fridge")
* Optional remarks and file uploads
* Click **Submit** to close out the corrective action

<figure><img src="https://2675140142-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPnSdrHOYeIaTHbt8Z0Qc%2Fuploads%2FBXjYM9mT1oOrgPgSAoQZ%2FScreenshot%202025-04-18%20at%202.41.12%E2%80%AFpm.png?alt=media&amp;token=1f353b70-6277-4cd7-8091-14c2020ebc1f" alt=""><figcaption></figcaption></figure>

<figure><img src="https://2675140142-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPnSdrHOYeIaTHbt8Z0Qc%2Fuploads%2FrTAxvxlJmeowjnnn1RSS%2FScreenshot%202025-04-18%20at%202.41.21%E2%80%AFpm.png?alt=media&amp;token=3678338b-bd4c-4c6d-82e0-1bd52866fb74" alt=""><figcaption></figcaption></figure>

***

### 6. Other Functional Features

#### Snooze Alerts

* Options to snooze alarms for 3, 6, or 12 hours
* Useful during:
  * Cleaning
  * Stock rotation
  * Maintenance periods

#### Maintenance Mode

* Permanently suspends alarms for a sensor
* Use only when:
  * Sensor is being serviced
  * Unit is offline for repairs

> ⚠️ Use with caution: Alarms are completely disabled while in maintenance mode.

***

### 7. Record Keeping

* Each submission is added to a central **data table**
* Export options:
  * **CSV** for bulk data processing
  * **PDF** for printed reports or audit documentation

<figure><img src="https://2675140142-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPnSdrHOYeIaTHbt8Z0Qc%2Fuploads%2FldASEu8jMRpdgJ0PMtWT%2FScreenshot%202025-04-18%20at%202.48.58%E2%80%AFpm.png?alt=media&amp;token=4adaf7ae-e5ce-4ad1-b3db-6c16857448a0" alt=""><figcaption></figcaption></figure>

***

### 8. Summary

Corrective actions are designed to:

* Ensure compliance with food safety protocols
* Provide traceable, timestamped documentation of responses
* Minimize operational disruptions while maintaining standards

Admins can customize the default actions and tolerances to align with internal food safety programs.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.didge.io/home/foodcore-sensors/end-user/core-functions/alerts-and-actions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.