Skip to Content
Docs

Run plan

When agents work, with the schedule of each job, working windows and weekdays, pausing, and asking for a run now.

The run plan shows when each agent works for a company and lets you hold it back. You can pause a job, limit it to certain hours and weekdays, or ask for one run now. None of this changes what an agent is allowed to do. It only changes when.

On the way

The run plan is the newest part of Agents. It is built and tested, and it reaches pilot companies with an upcoming release. This page describes it as built.

How agents are scheduled

Each agent owns one or more jobs, and each job wakes on a fixed rhythm that comes with the product. A job checks whether there is work, for example new purchase invoices or invoices that became overdue, and opens decision cards for what it finds.

The run plan adds your company's wishes on top of that rhythm. It is kept per company and per agent.

What the plan shows

For each job of an agent, the plan lists:

  • Rhythm. How often the job wakes.
  • Working window and weekdays. The hours and days in which it may work for this company.
  • Next expected wake. When the job is next due.
  • Liveness. Whether the job is running on time. A job that is late or stuck is shown as such, never hidden.

Below the jobs you find two lists.

  • Run history. The last 50 runs of the agent in this company: start time, what triggered the run (a person, the schedule or an event), status, duration, steps, cost and the outcome in one sentence. Each row links to the cards the run produced.
  • Outbound effects. What the agent sent outside the company, newest first, with the delivery status. For the Collections agent these are the reminder letters.

Pause, windows and weekdays

You can change three things per job.

  • Pause and resume. A paused job does no new work for this company until you resume it.
  • Working window. A start and end time in the company's local time.
  • Weekdays. The days on which the job may work.

Pausing and narrowing never give an agent more authority, so one person with the right to manage agents can do it alone. Widening the window back to the product default also takes one person. Every change is written to the audit trail with the values before and after.

Three things stay as they are while a job is paused:

  • Open decision cards stay open and can still be signed.
  • Autonomy levels and the way they are raised do not change. See autonomy levels.
  • The kill switch remains the only control that stops everything at once. See agents.

Some jobs cannot be split by company

A few background jobs serve the whole tenant and cannot follow a plan for one company. Such a job says so in the plan. It does not pretend to be paused.

Overnight windows

A window may cross midnight, for example 22:00 to 06:00, so an agent prepares its cards before the working day starts.

The weekday is judged by the company's local date at that moment, and not by the day the window started. A window of 22:00 to 06:00 that is limited to Monday covers Monday from 22:00 to midnight only. For the hours from midnight to 06:00 on Tuesday, tick Tuesday as well. The form reminds you of this.

Some agents have hours of their own that a plan cannot widen. The Collections agent sends reminders only between 08:00 and 10:00 on the company's local clock, and never on the due date itself. If the company's time zone is unknown, it sends nothing.

Run now

When you do not want to wait for the next wake, ask for a run.

Ask for the run

Choose the job and ask for a run now. Tosven records who asked and when. There can be one open request per company, agent and job.

The run starts on the next round

Nothing runs in your browser. The background worker picks up the request at the start of its next round and runs that job for your company only. Your right to manage agents is checked again when the run starts.

Read the result

The run appears in the run history, marked as started by a person, with links to its cards.

Three rules apply:

  • One request, one run. A request never starts more than one run.
  • A wait of 5 minutes. After a request, the same job cannot be requested again for 5 minutes.
  • A person still decides. Cards from a run that a person started always go to a person for approval, even where a published rule and the autonomy level would allow an automatic decision.

A request can be refused, and the refusal says why: the job is paused, the agent is stopped by the kill switch, the 5 minute wait has not passed, or the job cannot run for a single company.

Next steps

  • Agents: the roster, managers and the kill switch.
  • Decisions and approvals: what to do with the cards a run produces.
  • Command: the morning board where the results of the overnight work appear.

On this page