Statuses

Introduction

Scenario statuses help you quickly understand the current state of a Website scenario.

Scenario statuses

Status	Description
Not recorded	No steps have been recorded for this scenario yet.
Recorded	Scenario steps have been recorded and are ready for execution.
Valid	The scenario configuration is valid and ready, but the scheduler is not set.
Queued	Manual execution has been triggered. The scenario is queued until the current scenario execution completes.
Processing	The scenario is currently being processed, such as during execution or while generating related assets (for example, thumbnails).
Pass	The scenario ran successfully and all steps passed. Next runs are scheduled.
Error	Scenario execution failed due to errors in one or more steps. The configured Failures to alarm threshold was reached, triggering the Error status.
Acknowledged	The scenario was in an Error state, but the issue has been acknowledged.

Where statuses appear

Scenario statuses are visible in several places in TestCLIX:

Workspace – in the workspace tree, each scenario displays a colored status indicator (dot) showing its current state. In workspace grid and table views, the current scenario status is displayed as a status badge, such as Pass, Error, or Acknowledged.
Scenario overview – the Overview tab displays the current scenario status together with execution and evaluation details.
History – the History tab shows how the scenario status changed over time and how individual runs affected it.

History

The History tab combines two types of information:

Run history – individual scenario executions
Status changes – transitions between scenario statuses

This helps track both execution failures and the resulting status updates.

Runs in evaluation period

The Runs in evaluation period section displays scenario executions included in the current evaluation window.

It also shows:

Scenario status – the current overall scenario state.
Evaluation period – the time range used for evaluation.
Failures to alarm – the number of failed runs required before the scenario enters the Error status.

When the configured failure threshold is reached, TestCLIX changes the scenario status to Error.

For more information, see Alarm and Notifications.

Run status

Run status represents the result of a single scenario execution. This is the default filter in the Scenario history section.

Each run entry includes:

Trigger – how the run started
Executed at – execution timestamp
Message – execution details or failure reason
Run status – execution result, such as Error or Pass
Revision – scenario revision used during execution

Trigger types

Trigger	Description
	Started manually by a user.
	Started automatically by the configured scheduler at a defined interval or time.
	Started automatically by TestCLIX as part of an internal system action, such as thumbnail generation or other background processing.

Status change

Status changes describe transitions between scenario states. This is another filter in Scenario history.

Examples:

Error → Acknowledged
Acknowledged → Error
Error → Pass

Each record contains:

Info – additional context
Executed at – when the change happened
Message – transition reason
Status change – previous and current status

Common messages include:

Manually acknowledged
Test recovered
Test failed

Manual acknowledgement

When a scenario enters the Error status, you can acknowledge the error to indicate that the issue is known and is being handled. You can acknowledge an error in one of the following ways:

Three-dot menu
Top action panel

Locate the scenario you want to update.
Open the three-dot menu.
Select Mark error as acknowledged.

The acknowledgement is recorded in History as a status change entry with the message Manually acknowledged.

If a later run succeeds, TestCLIX automatically updates the scenario status and adds an entry such as Test recovered.