> 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-an-event/at-startup.md).

# At startup

**Category:** Trigger

**Version:** 1.0

**Last updated:** January 28, 2026

**Author:** Any2Info

***

### Description

The **At Startup trigger** starts a dataflow automatically when the DataHub service starts.

When this trigger fires depends on how the DataHub is hosted:

* **Windows Service**\
  The trigger is raised when the Windows service is started or restarted.
* **IIS Website or Virtual Application**\
  The trigger is raised when the application pool is started or recycled.

This trigger executes **only once per application lifecycle**.\
While the DataHub remains running, the startup event will not be raised again.

If the DataHub fails to start and is restarted, the startup event is raised again.

***

### Configuration Options

| Setting         | Required | Description                                                                                                                                                 |
| --------------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Repeat every    | No       | Enables repeated execution starting from the moment the DataHub has started. The interval supports Seconds, Minutes, Hours, Days, and Weeks.                |
| For duration of | No       | Defines how long the repeated executions should continue. Can be set to **Indefinitely** or a specific duration in Seconds, Minutes, Hours, Days, or Weeks. |
| Random delay    | No       | Adds a random delay before the first execution after startup. The delay value supports Seconds, Minutes, Hours, Days, and Weeks.                            |

***

### Usage

Use the **At Startup trigger** when actions need to be performed automatically whenever the DataHub starts or restarts.

Typical use cases include:

* Informing an administrator or user that the DataHub has started
* Clearing caches when the DataHub restarts
* Testing external connections when the DataHub becomes available

This trigger can be used in **multiple dataflows**.\
All dataflows that use the At Startup trigger will be triggered when the DataHub starts.

A dataflow can contain **only one trigger**.

***

### Tips & Best Practices

* Use **Random delay** when multiple startup-triggered dataflows perform heavy operations to avoid load spikes.
* Configure **Repeat every** only when repeated execution after startup is required.
* Do not assume this trigger will fire again unless the DataHub is restarted.

***

### Changelog

| Version | Date             | Change                               |
| ------- | ---------------- | ------------------------------------ |
| 1.0     | January 28, 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-an-event/at-startup.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.