> 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/weekly.md).

# Weekly

**Category:** Trigger

**Version:** 1.0

**Last updated:** Januari 5, 2026

**Author:** Any2Info

***

### Description

The **Weekly trigger** starts a dataflow automatically based on a weekly schedule.

### 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 exact date and time at which the dataflow will execute once.</td></tr><tr><td><strong>Recur (days)</strong></td><td>Yes</td><td>Number of weeks between executions (e.g. <code>1</code> = every week, <code>2</code> = every two weeks).</td></tr><tr><td><strong>Weekdays</strong></td><td>No</td><td>One or more days of the week on which the dataflow should run (Monday through Sunday).</td></tr><tr><td><strong>Repeat every</strong></td><td>No</td><td>Optional. Enables repeated execution after the start time. The interval 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 delay</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 the **Weekly trigger** when a dataflow needs to run on specific days of the week, optionally repeating every multiple weeks.

Typical use cases include:

* Weekly data synchronization
* Scheduled batch processing
* Regular maintenance tasks

***

### Tips & Best Practices

* Select at least one weekday to ensure the trigger executes.
* Use recur (days) = 1 for standard weekly schedules.
* Limit repeat every unless multiple executions per day are required.

***

### 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.