Error codes
Every failure has one of these codes. They’re stable, so scripts and AI agents can rely on them.
| Code | Means | What to do |
|---|---|---|
ELEMENT_NOT_FOUND |
No visible element matches the selector | Check did you mean; sis inspect the app |
AMBIGUOUS_SELECTOR |
Several elements match; all are listed | Scope with >> or use a more exact name |
NOT_INTERACTABLE |
Found, but disabled or covered (by what is named) | Close what’s on top, or wait for it to be enabled |
ASSERTION_FAILED |
An expect never came true; expected and actual are shown |
Decide whether the app or the test is wrong |
TIMEOUT |
A wait or the step ran out of time | Is the app slow? Raise the step’s timeout: if that’s expected |
APP_LAUNCH_FAILED |
The app didn’t start, or a reuse.check failed twice |
Check the app’s config, URL or server |
APP_NOT_RUNNING |
The app quit or crashed during the test | Look at the app’s own logs |
PERMISSION_DENIED |
macOS blocked access | Grant Accessibility; see Install |
NOT_SUPPORTED |
The step isn’t possible on this platform or app kind | See Platform support |
NOT_IMPLEMENTED |
A reserved feature (ai:) |
|
INVALID_TEST |
The file is wrong (a missing file to drop, bad options) | sis validate |
VARIABLE_UNDEFINED |
A ${…} has no value |
Set it in vars, the environment, or --var |
COMMAND_FAILED |
A run: exited with a code not in code:; stderr is shown |
Fix the command or script |
FLOW_NOT_FOUND |
call: names a flow that doesn’t exist |
Check the name; sis list |
RUNTIME_MISSING |
The browser runtime isn’t installed | sis setup |
DIALOG_OPEN |
A browser alert, confirm or prompt is open | Answer it: click: dialog >> button "OK" |
DRIVER_ERROR |
An unexpected error | Retry; report it with the run folder if it persists |
SKIPPED |
Not a failure: the test didn’t run here, and says why (os: names other systems) |
Run it on one of those systems |
A11Y_VIOLATION |
a11y: strict and the accessibility check found a problem |
See Accessibility checks |
Made by
© 2026 Bussin Bytes Ltd · sisyphus.bussinbytes.io
