Skip to main content

​
Schedule Optimizer

The Schedule Optimizer converts business timing requirements into optimal cron expressions, handling timezone complexities, load distribution, and conflict detection.

​
Quick Reference

PropertyValue
DomainAutomation
FORGE Stage3 (Documentation)
Version1.0.0
Primary OutputOptimized cron expression + trigger config

​
Overview

Use this agent when: You need to schedule workflows with optimal timing, timezone handling, and resource distribution.
The Schedule Optimizer ensures your workflows run at the right time:
  1. Cron Optimization: Convert business requirements to cron
  2. Load Distribution: Spread executions to avoid contention
  3. Conflict Detection: Identify scheduling conflicts
  4. Timezone Handling: Correct behavior across zones and DST

​
Core Capabilities

Cron Optimization

Convert timing requirements to optimal cron expressions

Load Distribution

Spread workflow executions evenly

Conflict Detection

Identify and resolve schedule conflicts

Timezone Handling

Handle DST and timezone conversions

​
When to Use

​
✅ Use Schedule Optimizer for:

  • Daily/weekly/monthly reports
  • Business hour automation
  • Timezone-aware scheduling
  • Resource-intensive workflows needing load balancing
  • Complex recurring patterns

​
Common Patterns

Business NeedCron ExpressionTimezone
Every weekday 9 AM EST0 14 * * 1-5UTC (EST+5)
First Monday of month0 10 * * 1#1Local
Every 4 hours, business hours0 9-17/4 * * *Local
Last day of month0 10 L * *UTC

​
Usage Examples

Use the Schedule Optimizer to schedule daily sales reports:
- Run every weekday at 9 AM Eastern Time
- Avoid execution during DST transitions
- Distribute load across multiple report workflows
Output:
{
  "schedule": {
    "cron": "0 14 * * 1-5",
    "timezone": "UTC",
    "description": "Weekdays 9 AM EST (14:00 UTC)"
  },
  "rationale": "Converts EST to UTC accounting for DST",
  "loadAnalysis": {
    "estimatedDuration": "5 minutes",
    "conflictsWith": [],
    "resourceImpact": "low"
  }
}

​
Outputs

​
Schedule Configuration

{
  "meta": {
    "generatedBy": "schedule-optimizer",
    "version": "1.0.0",
    "optimizedFor": "load-distribution"
  },
  "schedule": {
    "cron": "0 14 * * 1-5",
    "timezone": "UTC",
    "description": "Weekdays 9 AM EST",
    "nextExecutions": [
      "2026-03-11T14:00:00Z",
      "2026-03-12T14:00:00Z",
      "2026-03-13T14:00:00Z"
    ]
  },
  "rationale": {
    "timezoneConversion": "EST (UTC-5) → UTC",
    "dstHandling": "Executed in UTC to avoid DST issues",
    "loadDistribution": "Offset by 2 minutes from similar workflows"
  },
  "conflicts": {
    "detected": false,
    "nearbySchedules": []
  },
  "n8nConfig": {
    "nodeType": "n8n-nodes-base.scheduleTrigger",
    "parameters": {
      "rule": {
        "interval": [
          {
            "field": "cronExpression",
            "expression": "0 14 * * 1-5"
          }
        ]
      },
      "timezone": "UTC"
    }
  }
}

​
FORGE Gate Compliance

​
Entry Gate

  • Timing requirement specified
  • Timezone context provided
  • Existing schedule inventory available

​
Exit Gate

  • Optimized cron expression with rationale
  • Trigger configuration for n8n
  • Conflict analysis completed
  • Load distribution recommendations provided

​
Best Practices

Store and execute schedules in UTC to avoid DST complexity. Convert to local time for display only.
If you have 10 daily reports at 9 AM, stagger them (9:00, 9:02, 9:04…) to avoid resource spikes.
If a workflow takes 10 minutes, don’t schedule the next one for 9:05 AM.
Verify behavior during spring forward (lost hour) and fall back (repeated hour).

​
Integration Points

​
Control Plane API

EndpointPurpose
GET /api/v1/workflows/schedulesQuery existing schedules
GET /api/v1/metrics/execution-timesGet average execution times

​
Veritas Integration

Consumes:
  • vrt-c3d4e5f6: Scheduling best practices
  • vrt-g7h8i9j0: Resource optimization strategies
AgentRelationship
Workflow ArchitectDesigns overall workflow with schedule trigger

​
Source Files

Agent Definition

View full agent markdown