Retest Configuration for Scheduled Tasks
Overview
In ZetaSafe, scheduled tasks can be configured to automatically trigger additional tasks when certain conditions are met — for example, when a task cannot be completed or when a result falls outside of specification. These retest tasks ensure that failures and non-compliance are followed up appropriately without requiring manual intervention.
Note: Retests can only be configured for tasks that have a schedule. Tasks without a schedule cannot use this feature.
Retest Trigger Conditions
There are two conditions that can trigger a retest:
Trigger | Description |
Unable to Complete | The task could not be completed during the scheduled visit |
Out of Specification (OOS) | The task was completed but the result was marked as Red, indicating it failed to meet the required specification |
Task types can be configured to trigger a retest on either condition, both conditions, or neither.
How to Configure Retests
Retest settings are applied within the compliance scheme, either when a task type is first created or at any point during editing. Contact your ZetaSafe System Administrator if you need assistance configuring retest settings.
Retest Scheduling Rules
ZetaSafe applies the following logic when determining whether a retest should be triggered:
If a scheduled task exists on the same day as, or before, the date a retest is due, the retest will not be triggered. ZetaSafe treats the upcoming scheduled task as the retest.
Example
A task is scheduled every 7 days (e.g. every Monday). A retest is configured to trigger 14 days after a failure.
In this scenario, the retest will never be triggered — because there will always be another scheduled task within 7 days of the failure, ZetaSafe considers that task to be the retest and suppresses the additional one.
Tip: When configuring retest intervals, ensure the retest due date falls before the next scheduled occurrence. Otherwise, the retest will consistently be suppressed by the regular schedule.
Things to Keep in Mind
Retests require a schedule — this feature is not available for unscheduled tasks.
Configuration is done at compliance scheme level — retest settings apply to the task type, not to individual assets.
Retest suppression is by design — if a scheduled task is due before the retest, ZetaSafe intentionally suppresses the retest to avoid duplication. Review your retest intervals carefully to ensure they work as intended alongside your regular schedule.