Alerts and operational notifications
Alerts help teams identify upcoming, active, and overdue work derived from protocol timing and workflow scheduling.
Alert states
| State | Meaning |
|---|---|
| Upcoming | A scheduled action is approaching its execution window. |
| Active | The action is currently due or requires attention. |
| Overdue | The expected window has passed without completion. |
| Resolved | The related action was completed, cancelled, or otherwise resolved. |
Where alerts come from
Alerts may be created from workflow protocol offsets, step timing, batch schedules, sample schedules, review requirements, and other enabled operational rules.
An alert is not automatically a deviation or nonconformance. The organization should define when lateness or missed timing requires a compliance event, investigation, justification, or corrective action.
Working with alerts
- Review upcoming alerts during daily planning.
- Open the linked batch, sample, protocol step, or review item.
- Complete the required action or document why it cannot be completed.
- Escalate repeated or critical overdue items according to procedure.
- Review alert history during closeout and process improvement.
External destinations
FlaskTrack can deliver enabled notifications to external messaging systems. Configure and test each destination separately:
Do not send confidential scientific or personal data to a channel unless the destination and membership are approved for that data.
Audit and retention
Alert creation and state changes may be associated with auditable operational records. External messaging systems have their own retention, access, and deletion behavior; a message in Slack, Discord, or Matrix is not the authoritative FlaskTrack record.