Test & keep current
Monitoring and older results
Decide how often to repeat a test and how long an earlier result should be treated as current. These are separate settings.
Last reviewed 23 October 2026
Search runs in your browser. No account needed.
Choose a test schedule
You can choose a schedule when adding a workload or under Workload options → Monitoring policy. On demand runs only when someone starts a test. Eligible plans can repeat tests daily, weekly or monthly.
The current scheduler generates and tests the selected, pinned workload definition and its approved test material. It does not yet rediscover AWS or detect every source change automatically.
Run a fresh discovery, review the workload selection and map, then test the updated workload. A repeating test of an older definition cannot tell you that the live source is unchanged.
Set an age limit
Review result after controls when an older passing result stops being treated as current. Choose a shorter period for frequently changing or critical workloads. This is a reminder to reassess; it does not mean a test failed.
Look at the last test time and the next scheduled run. The age of the result, a change to the workload revision and a failed check are different reasons to take action.
If a scheduled test cannot start
Open the workload and inspect its setup and last monitoring attempt. Missing material or required criteria can prevent a new run. Resolve the named issue and start a test yourself if you need reassurance sooner than the next scheduled attempt.
When the workload changes
Adding or removing resources creates a new revision. Editing criteria changes the check version used by future tests. Re-run the workload after relevant changes; do not reuse an old result as proof of a changed package or behaviour.
Scheduled source rediscovery, change classification and automatic evidence invalidation are the next step in the assurance loop. They are not included in the current repeating-test promise.