Running a goal
Start a run from the command line with spl run, sit with it while it streams, answer the question it parks on, and read the outcome. This page points at the full guide.
spl run starts a run as you and stays with it: every turn prints as it
happens, a question the run needs answered is put to you in place, and the
outcome prints when the run ends, with the diff if it changed a repository.
spl run "Record one note saying the walkthrough works, then stop."The full guide is Running work with spl run. It covers:
- what a run is and which member carries it out,
- what each streamed line means,
- what happens when a run parks on a decision, and how you answer it,
- the outcome and its exit codes,
- how a run is bounded (turns, budget, time, the declared tools),
- giving a run a declared repository, and the green check it then owes,
- what does and does not stop a run.
The old goal path
--legacy runs the pre-v0.217 path: the goal is filed as an intent, routed to
a member, and polled until something closes it. It exists only for callers
that depend on that shape. Prefer the seat.
Related
- Running work with spl run: the full guide.
- Your call: everything waiting on you, including parked runs.
- Evaluating members: judging the runs a member did.
Debugging Syncropel
When something isn't doing what you expect — instance won't respond, a task is stuck in the wrong status, a record didn't route — this is the order to reach for tools.
Running work with spl run
Start a run as yourself, watch it stream to your terminal, answer the question it parks on, and read the outcome (with its diff when it changed a repository). How a run is bounded, and how one stops.