Summary
Enable agents to have multiple scheduled trigger times within the same day (e.g. 9:00 AM, 12:00 PM, 4:00 PM), rather than being limited to a single schedule per day. This allows users to receive multiple, timely updates for time-sensitive workflows.
Problem
Currently, agent scheduling appears to support only a single trigger per day. For use cases where users need periodic updates (e.g. morning summary, mid-day delta, end-of-day wrap-up), teams must create multiple near-duplicate agents or rely on manual runs and ad hoc reminders. This creates the following issues:
- Operational overhead: Duplicating agents to simulate multiple runs increases maintenance and risk of configuration drift across copies.
- User fatigue: Users either receive too much information in one drop or miss timely insights when information is most actionable.
- Loss of timeliness: A single daily update cannot accommodate workflows that evolve throughout the day (e.g. on-call changes, ticket intake spikes, deployment windows, SLA nearing breaches).
- Governance gaps: Workarounds (like external schedulers pinging webhooks) add complexity and bypass native auditability and permissions.
Impact
Supporting multiple schedules per day will:
- Improve decision latency and responsiveness by aligning updates with key moments in the day (start-of-day, mid-day, end-of-day).
- Reduce admin overhead by eliminating the need to clone and maintain multiple agents just for scheduling.
- Increase adoption and trust for time-sensitive agent use cases (IT operations, incident management, sales pipeline checkpoints, customer support SLAs, and exec briefings).
- Provide cleaner observability and governance by keeping scheduling native to Glean rather than relying on external schedulers.
