Automation and testing

Read reports and diagnose problems

Report state	Meaning
RUNNING	The scenario has not finished.
SUCCEEDED	The run completed and all defined assertions passed.
FAILED	An assertion did not meet its count bounds.
ERROR	An operational failure prevented normal completion.
CANCELLED	The run was cancelled.
INCOMPLETE	Required runtime evidence was lost or could not be collected reliably.

Reports contain the seed, baseline asset references, runtime version, assertion counts, and error classification. They do not include packet payloads or configured expected SET values. JUnit XML distinguishes failed assertions from execution errors, so a test pipeline can report both correctly. Upload report.xml as a JUnit test result after a local run.

The event list retains up to 10,000 display events. Read pages with after set to the previous nextCursor and limit between 1 and 1,000. droppedEvents reports retention loss. Assertions are counted as events arrive before old display events are evicted, so retention loss alone does not erase previously counted assertions. Runtime saturation or missing evidence must not be treated as a passing test.

Reopening a workspace recovers stored lab definitions and reports but leaves agents stopped. Interrupted operations are marked failed. Start agents explicitly after a server restart. SNMPv3 engine boots persist and increase across restart and reset; reset restores simulation values without reusing old SNMPv3 engine state.

Problem	What to check
Java reports an unsupported class version	Select a Java runtime compatible with your installed JARs; Release 1 requires at least Java 21.
LICENSE_INVALID or LICENSE_CAPACITY	Use a valid signed simulator license and stay within its agent count. Delete unused labs to release reservations.
Workspace cannot be opened	Check write access and whether another process holds the workspace lock. Use a separate workspace per process.
Agent cannot start or SNMP times out	Check the bind address, occupied UDP port, community/context, agent state, firewall, and active loss/outage rules.
HTTP 409	Check lifecycle state and idempotency-key reuse. Stop the lab before scenario execution.
HTTP 400 or 422	Check JSON syntax, field names, IDs, value types, and scenario times. Inspect the error code.
HTTP 413	Management JSON is limited to 1 MiB; an uploaded asset is limited to 64 MiB.
HTTP 503	Check license capacity, service readiness, and whether shutdown is underway.
An accepted operation later fails	Poll its operation resource and inspect errorCode; HTTP 202 means acceptance, not completion.
A traffic assertion fails	Check polling intervals and time windows. Requests during an outage count as outage packets, not decoded requests.