Skip to content
Kindo Kindo Docs

Scheduled Agents

Scheduled agents are workflow agents that run automatically on a cron schedule. They are ideal for recurring tasks like daily reports, weekly compliance checks, or periodic data synchronization.

How Scheduling Works

Each scheduled agent is backed by a cron trigger that determines when it runs. Kindo uses standard 5-field cron expressions (minute, hour, day-of-month, month, day-of-week) and supports timezone-aware scheduling.

When you create a scheduled agent, you define:

  • A cron expression or natural-language schedule (e.g., “every Monday at 9 AM”)
  • A timezone for the schedule to run in
  • The workflow steps the agent executes on each run

Scaling Limits and Quotas

Scheduled agents have organization-level quotas to ensure platform stability. These limits apply to the total number of enabled scheduled agents across all users in your organization.

Default Limits

LimitDefault ValueDescription
Max scheduled agents5 per organizationTotal number of enabled scheduled agents allowed
Minimum run interval60 minutesShortest allowed interval between consecutive runs

How Quotas Work

  • Quotas are counted at the organization level, not per user.
  • Only enabled scheduled agents count toward the quota. Disabling a scheduled agent frees up a slot.
  • The quota is checked when creating a new scheduled agent or re-enabling a disabled one.
  • If your organization has reached its quota, the “Build Agent” button for scheduled agents will be disabled with an explanatory message.
  • Your current usage is displayed on the agent creation screen (e.g., “3 / 5 scheduled agents used”).

Requesting Higher Limits

If your organization needs more scheduled agents or shorter run intervals, contact your Kindo account representative or reach out to support. Limits can be adjusted per organization based on your plan and usage patterns.

Best Practices

Choose Appropriate Intervals

  • Hourly or less frequent schedules are recommended for most use cases.
  • Consider whether your data sources update frequently enough to justify shorter intervals.
  • Longer intervals reduce credit consumption and system load.

Design for Idempotency

Scheduled agents should produce consistent results when run multiple times. If a run fails or is retried, the agent should handle duplicate data gracefully.

Monitor Agent Runs

Review your scheduled agent run history regularly in the Agent Monitoring tab. Look for:

  • Failed runs that may need investigation
  • Runs that take unexpectedly long to complete
  • Agents that are no longer needed and can be disabled to free quota

Manage Your Quota

  • Disable unused agents rather than deleting them if you may need them again. Disabled agents don’t count toward your quota.
  • Consolidate similar agents where possible. A single agent with multiple steps is often more efficient than several single-step agents.

Creating a Scheduled Agent

  1. Navigate to the Agents tab and select Create an Agent.

  2. Choose Scheduled as the agent type.

  3. Configure your workflow steps (LLM steps, API actions, etc.).

  4. Set your cron schedule using the schedule builder or a cron expression.

  5. Select the timezone for the schedule.

  6. Save and enable the agent.

For a detailed walkthrough, see the Scheduled Vulnerability Report tutorial.

Next Steps