vio runs and vio logs, as for any other run.
Needs
vio 1.0.0 or later. vio redeploy refreshing the run-input contract needs
1.0.6. Check with vio --version.vio schedule takes the short id vio list prints,
the full id, a unique prefix of at least six characters, or the deployment’s exact name.
Set a schedule
Setting a schedule turns it on. A deployment has one schedule; setting it again replaces
it. Leave out
--input when you re-time a schedule and its saved input is kept.
--at, --tz and --input only work together with --every. On their own they are
refused with usage.invalid.
Run inputs
A scheduled run gets no caller to fill in the agent’s inputs, so an agent that declares required inputs needs them in--input. Pass inline JSON, or keep the payload in a file:
vio names the inputs it requires and shows
both forms — for example
This agent requires run inputs: topic. Pass them with --input '{"topic": …}' or --input @file.json.
The run contract is the list of inputs the deployed agent declares. vio redeploy refreshes
it from your current .vio, so after you add or change an input, redeploy before you set
the schedule’s --input. See Manage deployments.
In the shell, use --input @input.json. /schedule splits its arguments on
spaces and does not handle quotes, so inline JSON works there only when it has no spaces:
--input {"topic":"notes"}.
See, pause, resume and clear
on, off and clear take none
of the options above except --json. Pass one and vio refuses with usage.invalid.
How often you can schedule
Your plan sets the shortest interval between runs:
Viorant enforces this, not
vio. A schedule more frequent than your plan allows is refused
with schedule.interval_below_plan, and the message points at vio upgrade
(Your plan). If you move to a plan with a longer minimum, any
schedule that is now too frequent pauses, and shows as off (plan limit).
What to expect
- Only a running agent on Viorant Cloud can be scheduled. A stopped or failed
deployment is refused with
schedule.deployment_not_schedulable. - One run at a time. If a run is still going when the next one is due, that turn is skipped.
- Three failures in a row pause it. After three failed runs in a row the schedule turns
itself off, and shows as
off (paused after 3 failed runs). Fix the agent, then turn it back on withvio schedule <id> on. - Older deployments may need a redeploy. If showing a schedule ends with
Redeploy this agent to enable scheduling., runvio redeploy <id>first.
What scheduled runs cost
A scheduled run is an ordinary run of the agent:- An agent on Viorant credits spends credits from
your wallet on every scheduled run. That is why
vio help --jsonmarksvio scheduleasspendsCredits. - An agent on your own provider key runs on that key.
vioshows a warning line for these: if the key is revoked, the scheduled runs fail with no one there to see it.
Error codes
With--json, a failure is {"error":{"code":"…","message":"…"}}: