> For the complete documentation index, see [llms.txt](https://academy.any2info.com/any2info-academy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.any2info.com/any2info-academy/no-code-platform/data-studio/data-hubs/toolbox/trigger/on-a-schedule/daily.md).

# Daily

**Category:** Trigger

**Version:** 1.0

**Last updated:** Januari 5, 2026

**Author:** Any2Info

***

### Description

The **Daily trigger** starts a dataflow automatically on a daily schedule.\
It is used to run dataflows at a fixed time every day, optionally with advanced repetition or random delay settings.

This trigger is typically used for periodic processing, synchronization tasks or reporting workflows that must run on a predictable daily cadence.

### Configuration Options

<table><thead><tr><th width="187">Setting</th><th width="145">Required</th><th>Description</th></tr></thead><tbody><tr><td><strong>Start</strong></td><td>Yes</td><td>The date and time when the trigger becomes active and the first execution occurs.</td></tr><tr><td><strong>Recur (days)</strong></td><td>Yes</td><td>Number of days between each execution (e.g. <code>1</code> = daily, <code>2</code> = every two days).</td></tr><tr><td><strong>Repeat every</strong></td><td>No</td><td>Enables repeated execution within the same day. The interval value supports <strong>Seconds, Minutes, Hours, Days, and Weeks</strong>.</td></tr><tr><td><strong>For duration of</strong></td><td>No</td><td>Defines how long the repeated executions should continue. Can be set to <strong>Indefinitely</strong> or a specific duration in <strong>Seconds, Minutes, Hours, Days, or Weeks</strong>.</td></tr><tr><td><strong>Random delays</strong></td><td>No</td><td>Adds a random delay before execution. The delay value supports <strong>Seconds, Minutes, Hours, Days, and Weeks</strong></td></tr></tbody></table>

***

### Usage

* Use this trigger to run a dataflow automatically on a daily or multi-day schedule, optionally with repeated executions within the same day.

***

### Tips & Best Practices

* Use recur (days) = 1 for standard daily execution.
* Only enable repeat every if multiple executions per day are required.
* Avoid long repeat intervals combined with **Indefinitely**, unless continuous execution is intentional.

***

### Changelog

| Version | Date             | Change                               |
| ------- | ---------------- | ------------------------------------ |
| **1.0** | Januari  5, 2026 | Initial documentation version added. |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://academy.any2info.com/any2info-academy/no-code-platform/data-studio/data-hubs/toolbox/trigger/on-a-schedule/daily.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.