Understand Test tab results

Updated 19 October 2026 · For everyone using AutomatedOn

After you click Run test, each fetched record gets a row. This guide explains what you'll see.

Columns

Column	What it shows
Status	Where the record is up to (see below).
Your dataset's fields	One column per field in the dataset's Select list, showing the values as fetched.
Steps	A badge for each step the record would reach, for example Send Email, a rule type name, or No Rule Match. Where a step has several actions, there's a badge per action, such as SmsReminder → Course Reminder SMS. A dash means no step would run.
Summary	The summary of which rules matched, as used by the `$$RULESET_SUMMARY$$` token.
Issues	A warning badge, such as 1 issue, if an action would have a problem. Hover over it to read the details.
Inputs	A button, such as Inputs (12), that opens every value available to tokens for this record: its fields, rule values and parameters.
Time	How long the record took to process, in milliseconds.

Status	Meaning
Pending	Fetched, waiting to be processed.
Processing	Being processed now.
Done	Processed with no problems found.
Issues	Processed, but at least one action has a problem, such as a token with no value. Hover to read it.
Error	The record couldn't be processed. The Steps column shows Query Error and the reason is shown next to it.
Not processed	The test was stopped or ended before this record was reached.

A Query Error means a rule needed to look up extra data for the record and couldn't. Common reasons:

The lookup needs a value the record doesn't have, for example Unresolved parameter(s) StudentId in rule dataset query filter. (dataset 'Attendance').
The data source returned an error, shown as Data source query failed (…) followed by its response.
A rule dataset lookup timed out.

In a real run, a record with a query error fails and no steps run for it.

Issues are listed as the action's name followed by the problem, for example Course Reminder: Unresolved parameter in Body. Typical issues:

Unresolved parameter in Recipient, …in Recipient CC, …in Subject, …in Body or …in Sender: a token has no value for this record.
Sender domain must be example.com: the email's Sender isn't on your sender domain.
Unresolved parameter(s) … in API request '…' (body). The request was not sent.: an API request token has no value.

If a rule lookup replaced one of the record's values, that cell is highlighted. Hover over it to see the value the rules and actions actually used.

It doesn't send anything, so it can't tell you whether a send would be accepted.
It doesn't check phone number format or the SMS length limit.
It ignores the process's Schedule Expression.