Skip to content

Troubleshooting

Start with sis doctor: it checks the browser runtime and macOS permissions and says how to fix what’s missing.

“PERMISSION_DENIED” or desktop tests can’t see anything

Section titled ““PERMISSION_DENIED” or desktop tests can’t see anything”

macOS hasn’t given the app running Sisyphus the Accessibility permission (Device Control and Data Access on macOS 27+). Grant it to Sisyphus Studio, or to your terminal when you use sis, then restart that app. Studio’s Settings → macOS permissions has a button that opens the right pane.

Grant Screen Recording, then restart Sisyphus. Tests run without it; only the screenshots are skipped.

The browser runtime isn’t installed. Run sis setup (add firefox or webkit if your tests use them), or use Settings → Web runtime in Studio.

  • Web: is the app running at that URL? If Sisyphus should start it, add serve: { command: …, ready: <url> } to the app.
  • Desktop: check the bundle, app or exe in sisyphus.yaml. sis apps lists running apps with their bundle ids.
  • Reused apps: the app’s reuse.check failed twice. Run the test with --no-reuse to see whether the app or the check is at fault.

“ELEMENT_NOT_FOUND” for something that’s clearly there

Section titled ““ELEMENT_NOT_FOUND” for something that’s clearly there”
  • Read did you mean: the name is often slightly different (“Sign In” vs “Sign in”, a trailing “…”).
  • Run sis inspect <app> and copy the selector from there.
  • The element may be in a different window, dialog or app: scope it (dialog >> button "OK") or use in:.
  • It may have no accessible name at all; then fix that in the app, or use an id ("#save").

Several elements match. The error lists them; narrow with >> (listitem "Milk" >> button "Delete") or a more exact name.

The element is there but disabled, or something covers it. The error names what’s on top: usually a banner, a dialog or a menu to close first.

A browser alert, confirm or prompt is open and the step wasn’t about it. Answer it first: click: dialog >> button "OK".

A test passes alone but fails in the suite

Section titled “A test passes alone but fails in the suite”

Tests share something: data, a signed-in session, a window left open. See Flaky tests.

Some apps drop keys while busy. fill retypes once and fails if the field is still wrong. Add step_delay: 200ms to the app’s tests, or to that test.

Send the run folder (.sisyphus/runs/<id>/) to your Bussin Bytes contact: it has the result, screenshots and trees.

Made by Bussin Bytes© 2026 Bussin Bytes Ltd · sisyphus.bussinbytes.io