Skip to content
English
Submit a Support Issue
  • There are no suggestions because the search field is empty.

What are the Process Alert types in Weever Process?

Here is a list of the types of Process Alerts that are generated in Weever Process. 

Process Alert Types

Process Alerts are flagged events generated during a Live Process when something deviates from expected behaviour. They are visible in the Process Alerts section of Weever Process and are used primarily by supervisors and QA/QC reviewers to understand and resolve issues. Here is a list of the types of Process Alerts that are generated in Weever Process. 

1. Recurring Task Skipped

  • Generated when a recurring check is skipped rather than completed. 
  • The system tracks who skipped it, when, and for what reason. 
  • Even if the skip is intentional, it still creates a flagged alert for supervisor review. 
  • Late completions (done after the scheduled interval) also generate an alert. 

2. Critical Issue

  • A status that can be manually set on a task, or automatically triggered via task logic/task rules based on field values. 
  • For example, a critical issue can be triggered when a number field value falls outside a defined threshold, or when a reconciliation check across multiple recurring submissions detects a pattern (e.g., a value exceeding a limit across a run). 
  • It represents a high-severity escalation requiring attention.

3. Signature Override

  • Generated when a signature on a submission is removed or overridden. 
  • These are explicitly flagged as issues in the audit trail and process activity stream, and are tracked for FDA/compliance purposes. 

4. Task Status Override

  • Generated when a task's status is manually overridden by a supervisor or administrator. 
  • Like signature overrides, these are flagged as issues in the process event stream. 

5. Number Out of Range

  • Generated when a Number Check field value falls outside a configured acceptable range. 
  • These values are also highlighted in red in the recurring grid view and in Form Reports for easy visual identification during review.

6. Double-Blind Mismatch

  • Generated during a double-blind quality control check when two independent submissions for the same field do not match. 
  • The mismatched field value is displayed in red in the "show details" view. 

7. Submission Overdue

  • Generated when a recurring task submission is completed, but was submitted after its scheduled due time — meaning the check happened, but late. 
  • This is distinct from Recurring Task Skipped, where the check was manually skipped altogether. 
  • With Submission Overdue, the operator did complete the recurring check, but not within the required time interval configured in the Process Builder.