AI workflows can move from chat-triggered to scheduled

Recurring workflow requirements, runtime boundaries, and validation paths are now clearer for time-based use cases.

What changed

• A workflow can be defined for a recurring schedule rather than a chat trigger.
• Runtime and user-interface expectations are documented before implementation.
• Validation focuses on whether the recurring job remains bounded and reviewable.

Why it matters

Teams can assess a time-based AI workflow as a governed use case instead of treating scheduling as an afterthought.

Scope: A schedule does not grant a workflow more authority than its declared tools, permissions, and confirmation rules.