Scheduled runs
SoonNot shipped. A cron expression can be saved on an agent, and nothing dispatches it.
- ✓A cron expression can be stored on an agent; nothing reads it
- ✓No friendly schedule presets
- ✓No schedules tied to statutory due dates
- ✓Manual and email triggers work today
What it is.
An agent can carry a cron expression. No scheduler reads it. The task that would run an agent on a schedule exists and is registered with the job runner, and no code path ever enqueues it — so a cron-triggered agent never fires.
We would rather correct this page than leave a schedule sitting in an agent looking as though it is doing something. Plenty of scheduled work does run inside LexVio — obligation reminders, the morning task digest, contract expiry and notice-deadline sweeps, health-score snapshots, retention purges — but none of it is a customer-defined agent schedule.
Three steps.
End to end.
There is no working agent scheduler.
Run on demand, or forward a document to the agent's own inbox address.
Contract obligations and tasks have real reminder jobs, and the contract lifecycle sweep flags expiries and notice deadlines on its own.
What you get.
- ✓A cron expression can be stored on an agent; nothing reads it
- ✓No friendly schedule presets
- ✓No schedules tied to statutory due dates
- ✓Manual and email triggers work today
- ✓Per-run records exist for the runs that do happen; there is no re-run action
Quick answers.
No. It will be saved and never dispatched. That is the whole of this page.
Not on this product. Contract-derived deadlines — obligations, expiries, notice deadlines — are tracked and reminded; statutory filing dates are not.