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
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
1.0
January 28, 2026
Initial documentation version added.
Last updated
Was this helpful?