Skip to main content
TripleBits Apprentice - Software for Agents

Menu

Sign In Register

Schedule Agent Runs

Create cron-based scheduled runs for Apprentice agents with prompts, max duration, run-now testing, and provider-supported tool-call turn limits.

15 views

Schedule Agent Runs

Schedules let an Apprentice agent run automatically from a cron expression.

Use schedules for repeatable work: daily summaries, periodic checks, report generation, inbox review, maintenance reminders, or any task where the same prompt should run on a regular cadence.

Before You Schedule An Agent

Make sure the agent already works manually.

Check:

  • Docker is running.
  • The provider and model are working.
  • The agent has the right folder access.
  • Permissions and capabilities are narrow enough for unattended runs.
  • Budget controls are set if the model or tools can cost money.

Do not make a new agent scheduled before you have reviewed at least one manual run.

Open Schedules

Open the agent, then select Config > Schedules.

The Schedules tab shows existing schedules and lets you add, edit, enable, disable, run now, or delete schedules.

Create A Schedule

Select Add Schedule, then set:

  • Name: a short label for the schedule.
  • Schedule: a cron expression.
  • Prompt: the work the agent should perform every time the schedule runs.
  • Max duration: how long the scheduled run may continue.
  • Tool turns: optional, if the selected provider supports backend tool-call turn limits.

The default schedule expression is:

*/30 * * * *

That means every 30 minutes.

Write A Good Scheduled Prompt

Scheduled prompts should be explicit because no user is typing follow-up instructions at trigger time.

Include:

  • The exact job.
  • The allowed data source.
  • Whether the agent may change files.
  • Where it should write output, if any.
  • What to do when it is unsure.

Example:

Review the mounted docs folder and summarize files changed since the last run.
Do not modify files. Post a concise summary to the agent Activity log.
If no changes are found, say so briefly.

Use Max Duration

Every schedule has a max duration in seconds.

Use a shorter duration for simple checks and a longer duration for heavier jobs. If the agent often hits the max duration, review the prompt and scope before raising the limit.

Use Run Now

Use Run now after creating or editing a schedule.

This starts the schedule immediately without waiting for the next cron time. Review the result in Activity and Run Detail before leaving the schedule enabled.

Enable And Disable Schedules

Disabling a schedule keeps the configuration but stops future automatic runs.

Use disable when:

  • A provider is failing.
  • A budget is close to its limit.
  • A folder or integration needs reconfiguration.
  • The scheduled prompt needs revision.

Troubleshooting

If a schedule does not run, check that it is enabled and the cron expression is valid.

If a schedule starts but fails, open Activity and Run Detail for the failed run.

If the agent runs too long, lower the prompt scope or max duration.

If a scheduled run spends too much, set or lower the agent budget.

If the agent asks for permissions during scheduled work, tune the agent's permissions before relying on unattended runs.

Next Step

After schedules work, configure budget and cost controls for the same agent.