If something is not working, these steps cover the most common causes. Most issues come down to the command itself, its environment, or where data is stored.
First, confirm the command works in a normal terminal with the same working directory and environment. Check History for the run: its status, exit code, and captured output usually show exactly what happened.
A command that depends on a specific directory or environment variable will fail if those are not set on the saved command. Verify the working directory matches where the command expects to run.
Everything — commands, groups, schedules, and run history — is kept in a local SQLite database in your operating system's standard application data directory. Nothing is sent to a server.
A non-zero exit code means the command itself reported a failure. Ordito captures the code and output so you can reproduce the command in a terminal to debug it further.
If none of this helps, report it on GitHub. Include your OS, the command's working directory and environment, and the exit code and output shown in History.
