# Scheduled Triggers

{% hint style="success" %}
**Audience:** Administrators, Solution Architects, and Developers

**Purpose:** Explains each scheduled trigger type in <code class="expression">space.vars.Kizen\_company\_name</code>: what it does, when it fires, and the behavioral details that affect how <code class="expression">space.vars.automations</code> respond to time-based conditions.
{% endhint %}

## Overview

Scheduled triggers fire based on time rather than a user action or data change. Instead of responding to an event as it happens, scheduled triggers calculate when a future execution should occur and queue it accordingly.

### Activity Past Due

Fires when a scheduled activity's due date and time passes without the activity being completed.

<div data-with-frame="true"><figure><img src="/files/5vONvwwQQcMWuXOe2dGe" alt="" width="256"><figcaption></figcaption></figure></div>

This trigger is useful for <code class="expression">space.vars.automations</code> that need to escalate or follow up when an activity is not completed on time. For example, sending a reminder to the <code class="expression">space.vars.entity</code> owner or reassigning the activity after a defined grace period.

### On or Around Date

Fires based on a date field on a <code class="expression">space.vars.entity</code>, running a set number of days before or after that date.

<div data-with-frame="true"><figure><img src="/files/oEoKU3rXF4kTYlFjIPHi" alt="" width="249"><figcaption></figcaption></figure></div>

This is the most configurable scheduled trigger and has several behavioral characteristics that are important to understand before use:

* **Future scheduling only:** When the <code class="expression">space.vars.automation</code> is activated, <code class="expression">space.vars.Kizen\_company\_name</code> evaluates existing <code class="expression">space.vars.entities</code> and schedules future executions based on their current date field values. <code class="expression">space.vars.entities</code> whose date field values are already in the past at activation time will not have executions scheduled. This trigger is not retroactive.
* **Recalculates on field change:** If the date field value changes after an execution has been scheduled, the scheduled execution is recalculated to reflect the new date. Changing the field moves the scheduled run. It does not create an additional execution.
* **Business calendar interaction:** When a calculated trigger date falls on a non-business day, the execution is adjusted to the nearest business day as defined by your business calendar configuration. The actual execution date may differ from the raw calculated date when non-business days are involved.
* **Single-instance scheduling:** This trigger schedules only one future execution at a time. For recurring or annual patterns, the next occurrence is scheduled only after the current one fires. Multiple future occurrences are never queued simultaneously.
* **Daylight saving time nuance:** Scheduled execution times may appear to shift when a DST transition occurs between when the execution is scheduled and when it runs.

### Scheduled

Fires on a user-configured recurring schedule. Only available on Global <code class="expression">space.vars.automations</code>.

<div data-with-frame="true"><figure><img src="/files/ZW4lSmSk86eqIGd28VOp" alt="" width="261"><figcaption></figcaption></figure></div>

Because Global <code class="expression">space.vars.automations</code> do not run in the context of a specific <code class="expression">space.vars.entity</code>, this trigger initiates executions on a time-based cadence. For example, every day or every week, independently of any <code class="expression">space.vars.entity</code> event. It is the appropriate choice when an <code class="expression">space.vars.automation</code> needs to run periodically without being tied to a specific <code class="expression">space.vars.entity</code> change.

A common pattern for Global <code class="expression">space.vars.automations</code> is to assign a <code class="expression">space.vars.entity</code> variable at the start of the <code class="expression">space.vars.automation</code>, giving subsequent steps a <code class="expression">space.vars.entity</code> context to operate against even though the trigger itself is not <code class="expression">space.vars.entity</code>-scoped.

***

## What's Next?

Continue to [Webhook Triggers](/docs/concepts/agentic-workflows/agentic-workflow-triggers/webhook-triggers.md) to understand how <code class="expression">space.vars.automations</code> can be initiated by inbound HTTP requests from external systems.

<details>

<summary><strong>Related Topics</strong></summary>

* [Automation Triggers](/docs/concepts/agentic-workflows/agentic-workflow-triggers.md)
* [Action-Based Triggers](/docs/concepts/agentic-workflows/agentic-workflow-triggers/action-based-triggers.md)
* [Webhook Triggers](/docs/concepts/agentic-workflows/agentic-workflow-triggers/webhook-triggers.md)
* [Automation Code Steps](/docs/concepts/agentic-workflows/automation-code-steps.md)

</details>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://developer.kizen.com/docs/concepts/agentic-workflows/agentic-workflow-triggers/scheduled-triggers.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.